BZR operations hang or show malformed dialog

It is to the point now where every commit dialog is incomplete, i.e. there's no way to commit since there's no button to press.

I've tried uninstalling / reinstalling, etc. I swapped from Sun Java 1.6 back to 1.5 (gcj is not even on the system).

Any ideas on what to try next?

I've attached a screenshot to show what's going on.

I am having the same issue that Kenneth describes in his comment to this thread. Once I get to the commit window there is no place to continue and my window looks like his screenshot.

I am using Galileo (the PHP developer version) with bzr 2.0.

I am modifying a text file, then I right click on the file. I go to the team -> commit option.

The window opens up. I can edit the text fields just fine. The problem is there is no continue/commit/next/finish button.

Thanks,
Kyle

I thought it would be important to add:

Java 1.6 and Ubuntu 64bit Jaunty.

Thanks,
Kyle

Note: ss the original report is regarding Ganymede (3.4), I don't think your problem is strictly related or caused by Galileo (3.5) changes.

s/ss/as

Hi Renato,

Is there anything else I can do to help track this issue down? Submit another bug slip? Turn on a debugging plugin for eclipse so we can see the actual error?

Thanks,
Kyle

You may want to take a look at the error log view, and show it to ~verterok. Note that, as I said, the question about compatibility with Galileo seems not related to your issue at all, you may want to remove the association.

I'm not subscribed to this bug anymore, won't be notified of any changes.

Hi Kenneth, Kyle,

Apologize the delay

I wasn't able to reproduce the error, so I'm setting up 64bit Jaunty VM in order to catch this one.
Btw, I'm running Karmic 64bit, but using Sun's Java 6.

Are any of you using openJDK?

Thanks.

I'm running 32-bit Jaunty with sun-java6. This error has occurred for me in both 3.3 and 3.4 Eclipse, but has not yet occurred in Aptana Studio 2.x (based on Eclipse 3.5). If there is anything you need to help diagnose this problem, just ask.

The Eclipse installs have support for C++, Android, and Maemo in them, so there may be conflicts in there.

I am also using sun Java6.

By OpenJDK, do you mean the GCJ plugin that comes with Ubuntu?

Here is the error log produced by Eclipse:

!SESSION 2009-11-09 20:27:14.372 -----------------------------------------------
eclipse.buildId=M20090917-0800
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.php.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.php.product

!ENTRY org.vcs.bazaar.eclipse.core 4 -6 2009-11-09 20:27:35.233
!MESSAGE run() got an unexpected keyword argument 'location'
!STACK 0
org.vcs.bazaar.client.xmlrpc.XmlRpcCommandException: run() got an unexpected keyword argument 'location'
 at org.vcs.bazaar.client.xmlrpc.internal.XMLRPCCommandRunner.runCommand(XMLRPCCommandRunner.java:238)
 at org.vcs.bazaar.client.commandline.internal.Command.execute(Command.java:82)
 at org.vcs.bazaar.client.commandline.CommandLineClient.run(CommandLineClient.java:539)
 at org.vcs.bazaar.client.commandline.CommandLineClient.run(CommandLineClient.java:533)
 at org.vcs.bazaar.client.commandline.CommandLineClient.log(CommandLineClient.java:230)
 at org.vcs.bazaar.client.commandline.CommandLineClient.log(CommandLineClient.java:211)
 at org.vcs.bazaar.eclipse.core.commands.LogCommand.run(Unknown Source)
 at org.vcs.bazaar.eclipse.ui.decorator.BazaarLightweightDecorator.getLastLogMessage(Unknown Source)
 at org.vcs.bazaar.eclipse.ui.decorator.BazaarLightweightDecorator.decorateByType(Unknown Source)
 at org.vcs.bazaar.eclipse.ui.decorator.BazaarLightweightDecorator.decorate(Unknown Source)
 at org.vcs.bazaar.eclipse.ui.decorator.BazaarLightweightDecorator.decorate(Unknown Source)
 at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263)
 at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
 at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
 at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
 at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
 at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
 at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
 at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
 at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.vcs.bazaar.eclipse.core 4 -6 2009-11-09 20:27:35.258
!MESSAGE run() got an unexpected keyword argument 'location'
!STACK 0
org.vcs.bazaar.client.xmlrpc.XmlRpcCommandException: run() got an unexpected keyword argument 'location'
 at org.vcs.bazaar.client.xmlrpc.internal.XMLRPCCommandRunner.runCommand(XMLRPCCommandRunner.java:238)
 at org.vcs.bazaar.client.commandline.internal.Command.execute(Command.java:82)
 at org.vcs.bazaar.client...

Let me know if there is anything else I can add or help with.

~kyle

Hi Kyle,

On Fri, Nov 20, 2009 at 2:25 PM, Kyle Schweighauser <email address hidden> wrote:
> Let me know if there is anything else I can add or help with.
>
> ~kyle
>
Thanks for the logs.

What version of bzr and bzr-xmloutput are you using?

Regards

--
Guillermo Gonzalez
<http://launchpad.net/~verterok>

Hi Kenneth

> On Mon, Nov 9, 2009 at 10:09 PM, Kenneth Loafman <email address hidden> wrote:
> I'm running 32-bit Jaunty with sun-java6.  This error has occurred for
> me in both 3.3 and 3.4 Eclipse, but has not yet occurred in Aptana
> Studio 2.x (based on Eclipse 3.5).  If there is anything you need to
> help diagnose this problem, just ask.
>
> The Eclipse installs have support for C++, Android, and Maemo in them,
> so there may be conflicts in there.
>
I'm aware of some issues with m2eclipse and Q4E, but don't know of
issues with the listed plugins.

Are you getting the same errors as kyle?

What version of bzr and bzr-xmloutput are you using?

--
Guillermo Gonzalez
<http://launchpad.net/~verterok>

Hi Guillermo,

bzr is 2.0.2-1~bazaar1~jaunty(jaunty)

bzr-xmloutput is 0.8.3-0ubuntu1

I am also using sun java 6, Eclipse 3.5 on Ubuntu 64bit. If that helps.

Thanks,
Kyle

-----Original Message-----
From: Guillermo Gonzalez <email address hidden>
Reply-to: Bug 428838 <email address hidden>
To: <email address hidden>
Subject: Re: [Bug 428838] Re: BZR operations hang or show malformed
dialog
Date: Fri, 20 Nov 2009 19:09:20 -0000

Hi Kyle,

On Fri, Nov 20, 2009 at 2:25 PM, Kyle Schweighauser <email address hidden> wrote:
> Let me know if there is anything else I can add or help with.
>
> ~kyle
>
Thanks for the logs.

What version of bzr and bzr-xmloutput are you using?

Regards

--
Guillermo Gonzalez
<http://launchpad.net/~verterok>

Kyle Schweighauser, Director of Information Technology
Extanto,LLC. | 349 North Polk Street | Eugene , OR 97402
Office 541.515.6232
http://www.extanto.com/
http://twitter.com/extanto

Hi,

On Fri, Nov 20, 2009 at 4:27 PM, Kyle Schweighauser <email address hidden> wrote:
> Hi Guillermo,
>
> bzr  is 2.0.2-1~bazaar1~jaunty(jaunty)
>
> bzr-xmloutput is 0.8.3-0ubuntu1
>
> I am also using sun java 6, Eclipse 3.5 on Ubuntu 64bit. If that helps.
>
Hi Kyle,

The xmloutput version is quite old

Please try updating xmloutput, there isn't a release of 0.8.6 yet, but
you can get all the fixes if you install trunk (I think 0.8.5 should
work too)

Regards,

--
Guillermo Gonzalez
<http://launchpad.net/~verterok>

Cool thanks, will do.

I will let you know the results.

~kyle

Guillermo Gonzalez wrote:
> Hi Kenneth
>
>> On Mon, Nov 9, 2009 at 10:09 PM, Kenneth Loafman <email address hidden> wrote:
>> I'm running 32-bit Jaunty with sun-java6. This error has occurred for
>> me in both 3.3 and 3.4 Eclipse, but has not yet occurred in Aptana
>> Studio 2.x (based on Eclipse 3.5). If there is anything you need to
>> help diagnose this problem, just ask.
>>
>> The Eclipse installs have support for C++, Android, and Maemo in them,
>> so there may be conflicts in there.
>>
> I'm aware of some issues with m2eclipse and Q4E, but don't know of
> issues with the listed plugins.
>
> Are you getting the same errors as kyle?
>
> What version of bzr and bzr-xmloutput are you using?

bzr 2.0.2
bzr-xmloutput 0.8.4

...Ken

Hi,

On Fri, Nov 20, 2009 at 5:53 PM, Kenneth Loafman <email address hidden> wrote:
> Guillermo Gonzalez wrote:
>> Hi Kenneth
>>
>>> On Mon, Nov 9, 2009 at 10:09 PM, Kenneth Loafman <email address hidden> wrote:
>>> I'm running 32-bit Jaunty with sun-java6.  This error has occurred for
>>> me in both 3.3 and 3.4 Eclipse, but has not yet occurred in Aptana
>>> Studio 2.x (based on Eclipse 3.5).  If there is anything you need to
>>> help diagnose this problem, just ask.
>>>
>>> The Eclipse installs have support for C++, Android, and Maemo in them,
>>> so there may be conflicts in there.
>>>
>> I'm aware of some issues with m2eclipse and Q4E, but don't know of
>> issues with the listed plugins.
>>
>> Are you getting the same errors as kyle?
>>
>> What version of bzr and bzr-xmloutput are you using?
>
> bzr  2.0.2
> bzr-xmloutput  0.8.4
>
If you'r getting the same error as Kyle, please try updating
xmloutput, 0.8.5 should
work ok.

--
Guillermo Gonzalez
<http://launchpad.net/~verterok>

Ok, sorry I was away from this for so long. Work obligations and holiday caught up with me. I updated to bzr-xmloutput 0.8.4. The commit worked.

I got this NPE though.

java.lang.NullPointerException
at org.vcs.bazaar.eclipse.ui.operations.PushOperation.getPushLocation(Unknown Source)
at org.vcs.bazaar.eclipse.ui.operations.PushOperation.<init>(Unknown Source)
at org.vcs.bazaar.eclipse.ui.actions.CommitAction$3.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

I chose the option to push out to central server when I commited.

Error while executing commit

eclipse.buildId=M20090917-0800
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.php.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.php.product

I am going to get the 0.8.5 version that Guillermo suggested before. I will update once I have tested that version.

Thanks,
Kyle

I will have to test 0.8.5 later tonight or tomorrow night as launchpad is going offline for maintenance.

~kyle

I am still having this problem, just with newer versions.

Aptana Studio 2 (Eclipse 3.5.2 based)
bzr-xmloutput 0.8.7
bzr 2.3.4
sun-java6

Very frustrating. It works sometimes, quite well, then commit just stops working. Is there a fixed port that the bzr-xmlrpc uses? Anything fixed that would cause an allocation hang?

Hi all,

I have the same issue. I am using
Eclipse: Version: 3.5.2 Build id: M20100211-1343
Eclipse plugin for Bazaar: 1.1.1.210
I also installed: bzr-xmloutput-0.8.7

Sometimes when I click on commit no window appears and I have an error log in the error window (see file attached)
Sometimes the windows appear wihout any button but no error log in the error window...

Thanks for your help

I too am encountering the same issue as described above.

Using:
Eclipse Version: Helios Service Release 2, Build id: 20110218-0911
Eclipse Platform: 3.6.2.M20110210-1200
bzr Eclipse plugin: 1.1.1.210

I used bzr-xmloutput-0.8.7 with success - "okay" and "cancel" buttons appear on the Commit form when displayed and I haven't encountered the problems mentioned above, however, I primarily use bzr-explorer to execute version control operations. Therefore, the mention problems might exist but they go undiscovered.

I recently upgraded to bzr-xmloutput-0.8.8 and encountered both the missing buttons at the end of the commit form and the sporadic failure to render the Commit form as mentioned above. For now, I've returned to using bzr-xmloutput-0.8.7.

Just providing further information, it's not a burning issue for me due as my work flow relies on bzr-explorer.