Tasque Error when using Remember the Milk as Task Management System

[traist120]

Description: Ubuntu jaunty (development branch)
Release: 9.04
tasque:
  Installed: 0.1.8-1build2
  Candidate: 0.1.8-1build2
  Version table:
 *** 0.1.8-1build2 0
        500 http://us.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

I get this error when trying to sync with remember the milk.
Bad key or directory name: "/desktop/gnome/url-handlers/": Key/directory may not end with a slash '/'

[Michael Turquette (mturquette)]

I have replicated this bug on two separate machines both running Jaunty Beta. One is x86_64 and the other is x86.

[Pascal T (pthivent)]

I'm facing this bug too with Jaunty Beta on a x86 platform when I try to "authorize" Tasque to access RTM.

It looks like a little regression. Would be nice to fix this before the final release.

[PlaidRadish (jeff-plaidradish)]

Right there with you, guys. Where is the Tasque configuration file? Should "Remember the Milk" be in a .conf somewhere? Can it be manually added. What are our options? I'm using an Intrepid x64 and I'm in the same boat...not good.

redundant confirmation

[Krzysztof Janowicz (janowicz)]

i have the same issue, any ideas?

[Michael Turquette (mturquette)]

Has Ubuntu changed its gconf schema considerably since 8.10? It might
be a simple matter of adjusting for such a change.

Mike

On Mon, Apr 27, 2009 at 7:57 AM, Krzysztof Janowicz
<email address hidden> wrote:
> i have the same issue, any ideas?
>
> --
> Tasque Error when using Remember the Milk as Task Management System
> https://bugs.launchpad.net/bugs/337849
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “tasque” source package in Ubuntu: Confirmed
>
> Bug description:
> Description:    Ubuntu jaunty (development branch)
> Release:        9.04
> tasque:
>  Installed: 0.1.8-1build2
>  Candidate: 0.1.8-1build2
>  Version table:
>  *** 0.1.8-1build2 0
>        500 http://us.archive.ubuntu.com jaunty/universe Packages
>        100 /var/lib/dpkg/status
>
> I get this error when trying to sync with remember the milk.
> Bad key or directory name: "/desktop/gnome/url-handlers/": Key/directory may not end with a slash '/'
>

[Krzysztof Janowicz (janowicz)]

yes, maybe only a minor change is required but so far it does not work anymore

[slayton (slayton)]

I am getting this problem on a new install of tasque. I just installed Jaunty on my desktop then I installed tasque which isn't working.

On my laptop; however, I had tasque installed and working in Intrepid then I upgraded and tasque is still working fine on my desktop.

[Michael Turquette (mturquette)]

To be honest I haven't looked into the solution much. I got that
error, so I compiled the latest out of git. After building the head
of tasque's master branch I still received that error, but was able to
use tasque after quitting the app and reopening it.

This should not be considered as fixed, but for me at least I am able
to use tasque in its funky state.

Mike

On Thu, May 21, 2009 at 8:01 AM, neurostu <email address hidden> wrote:
> I am getting this problem on a new install of tasque. I just installed
> Jaunty on my desktop then I installed tasque which isn't working.
>
> On my laptop; however, I had tasque installed and working in Intrepid
> then I upgraded and tasque is still working fine on my desktop.
>
> --
> Tasque Error when using Remember the Milk as Task Management System
> https://bugs.launchpad.net/bugs/337849
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “tasque” source package in Ubuntu: Confirmed
>
> Bug description:
> Description:    Ubuntu jaunty (development branch)
> Release:        9.04
> tasque:
>  Installed: 0.1.8-1build2
>  Candidate: 0.1.8-1build2
>  Version table:
>  *** 0.1.8-1build2 0
>        500 http://us.archive.ubuntu.com jaunty/universe Packages
>        100 /var/lib/dpkg/status
>
> I get this error when trying to sync with remember the milk.
> Bad key or directory name: "/desktop/gnome/url-handlers/": Key/directory may not end with a slash '/'
>

[Erwin Junge (erwin-junge)]

I have also run into this problem.

I use two systems, one with jaunty x86_64 on it and one with UNR (which is x86) on it. Both display the behaviour and I haven't got a clue how to fix it. There is no config-file that I could locate that references anything close to the error message. Also searching in gconf-editor for "tasque" didn't help. If it is fixed in the master branch perhaps it would be a good idea to simply update the package in the repositories?

Greetings,

Erwin Junge

[Hugues Haubruge (ubuntu-haubruge)]

This problem is not limited to Tasque, see e.g. https://bugs.launchpad.net/ubuntu/+source/deskbar-applet/+bug/349106 and https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/365472.

According to the Tomboy developer this would be a GTK+ issue (http://bugzilla.gnome.org/show_bug.cgi?id=581582)

Anyway, one of the comment there advises to reset the url-handlers in gconf (by running:
$ gconftool-2 --recursive-unset /desktop/gnome/url-handlers)

A similar but less drastic approach is the following:
- launch gconf-editor
- uncheck the "enabled" box for /desktop/gnome/url-handlers/http and https (the latter is probably the only culprit)
- launch tasque (connection works after a warning - I clicked too fast to actually read what it said...)

One may enable again these handlers afterwards, the workaround still seems to work after closing and restarting Tasque.

[Erwin Junge (erwin-junge)]

The workaround mentioned by Hugues Haubruge worked for me as well, however I had to try multiple times.

The warning was exactly the same message for me. After the 4th try, firefox finally opened a new tab with the RTM security thing in it.

Confirmed to still work after re-enabling the handlers.

[parka (parkalewis)]

Thanks a lot for the workaround. It worked for me as well:

- I did not uncheck the http handler, just the https handler.
- After the 1st try, firefox opened and displayed the RTM message which I confirmed.
- Then I went back to the tasque dialogue which was still open and confirmed the message there.
- After re-enabling the https handler, it still works.

[Starfleet (starfleet)]

The workaround doesn't seem to work, if your are behind a proxy server that needs authorisation

[pak33m (pak33m)]

This problem happened for me but while I'm on Karmic. Just after running $ gconftool-2 --recursive-unset /desktop/gnome/url-handlers, as listed by Hugues Haubruge above Tasque immediately authenticated successfully and the tasks were refreshed without having to restart Tasque. However, i did restart Tasque just to check and the tasks were both present and able to be refreshed.

[Jean Jordaan (jean-jordaan)]

Just got me also, on Jaunty. Didn't manage to make the warning dialog go away, but I'm connected to RTM now. I guess this means that Tasque has very very very very very few users, on Ubuntu at least.

[Sandy Armstrong (sanfordarmstrong)]

Recommend filing an upstream bug so that Tasque developers are aware of the problem.

Also recommend attaching a patch to the hypothetical bug, which replaces LinkButton with Button.

[Sarah Sharp (sarah-a-sharp)]

I also have this issue, but none of the work-arounds helped me. I tried unchecking http and https. I also tried running `gconftool-2 --recursive-unset /desktop/gnome/url-handlers` and that did not work either.

I'm behind a proxy, if that matters. I have the system-wide proxy set through System->preferences->Network Proxy, and I also have an "export http_proxy=..." line in my .bashrc.

I'm running Lucid and using the 0.1.8-4 tasque package.

[Jack Leigh (leighman)]

Is this still an issue in a recent Ubuntu/Tasque release?
Thanks.

[Erwin Junge (erwin-junge)]

I have reinstalled Ubuntu since my previous report and since I no longer use RTM, I didn't bother to reinstall Tasque. This can therefore be regarded as a "clean install".

Steps taken:
1. Installed Tasque
2. Told Tasque to use RTM
3. Logged in to RTM
4. Clicked the "authorize" button in Tasque

Result:
Tasque is now functioning in concert with RTM. No error messages came up and no need for additional workarounds.

In my opinion, this issue is fixed and the bug can be closed.

Greetings,

Erwin Junge

[Jack Leigh (leighman)]

Please reopen by setting to 'New' if you still experience this in a recent release of Ubuntu/Tasque