Please package groundcontrol 1.6.5-1. [Launchpad now using openid breaks login]

I've created groundcontrol.log in my home folder and this are interesting parts from the output (IMO):

2-26 18:54 root DEBUG User found - you are logged in
02-26 18:54 root WARNING Unable to generate data from content.

02-26 18:54 root DEBUG -- Poll Quit configure --
02-26 18:54 root DEBUG Cancelled or no callback for window
02-26 18:54 root DEBUG Quit 'configure' Main Loop.

Here's my groundcontrol.log file after a login attempt.

I am also having the exact same error on latest version of Groundcontrol and fully updated Karmic.

This bug also occurs in lucid (and I can replicate it in karmic)

What is the solution for this bug? I assume there's still a way to log in through the API. Is there progress being made, or is this all on Launchpad's end?

There are 2 ways to patch the bug with hacks, I've been considering doing that. But they are guaranteed to break in the future in the same way.

Although I've been very busy with Anime Boston event, so don't worry, I haven't forgotten.

Is there a way to use GroundControl without logging in? At the moment, it's completely unusable.

It works if your already logged in, and it also works for branches you've already got checked out. But otherwise it's completely unusable.

Shouldn't something be shown to the user?. My example: this is the first time I'm trying GC and spent almost 10 minutes trying to login, but it wasn't working. As I didn't get any failure message I imagined that it should be a bug. So I logged in to LP and try to find a bug that could be mine and found this bug. If the UI showed me something like "Sorry, we were unable to log you in" and a details button with something like "Launchpad couldn't connect to openid" (or whatever) would have saved me - and made the new users easier.

I've installed groundcontrol to a fresh new Ubuntu install for managing my project. This bug doesn't let me fetch my project from launchpad. So.... until Martin, publish a fix, u can use the-already-installed "Olive Bazzar Branch Manager".

Just create a forlder under Projects, open terminal there, login with "bzr launchpad-login {user name}", and then open Olive Bazzar Branch Manager", go to the newly created folder, initialize branch, get your project... and start your hacking...

Martin, could we just have the user auth like they do in other OAuth applications? (ala ubuntu-dev-tools)

I don't think such usages were affected by this change, and I feel uncomfortable about having to support scripting the authentication using an "Undocumented API" (the login page) in a LTS release.

Luke: No, because without ssh support in OAuth, it won't work anyway.

Rock meet hard place.

Martin, what if we were to use OAuth for everything else, but when it comes to copying over the SSH keys put up a dialog:
    "Please copy and paste this into the resulting window which will open in your browser in a few seconds, press save, and return here."

That's not ideal, but I'm not sure we're going to be able to get write access to SSH keys in the near term (see bug 357235).

Is there anything else we cannot do via OAuth?

Luke: That's not just "not ideal", that's "no deal", Ground Control will not function under such restrictions. If SSH via OAuth can not be sought, then I will have to continue to log in via a fake web browser in order to implement it. This is Critical.

I've fixed the issue with black magic use of webkit, please install the daily build and test this fix.

Doesn't work for me. After entering my email/password, the browser only shows an "invalid OpenID transaction"

Works for me, but initially it displays incorrect information in the "login" dialog, I had to re-run lp-groundcontrol to get it working.

(using edge)

I just talked to doctormo who said we should wait to sync until 1.6.1-1 is available. That will fix 2 additional bugs.

Please see release 1.6.3

https://launchpad.net/groundcontrol/trunk/1.6

Is this ready to go yet?

It is ready to go.

Could you please clarify what is going on? What do you mean by "Please package"? It is already packaged. Is there a reason for transforming this bug from a sync request? Why isn't the new version being uploaded to Debian?

It will be, but Scott suggested that we upload this to Ubuntu due to time constraints.

nhandler: The version originally desired (and in Debian) got superceded due to new bugs getting fixed, so I told them to do a direct upload to Ubuntu. I can't guarantee any more syncs will get done.