[JBoss JIRA] (JBIDE-20111) Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20111:
--------------------------------
Summary: Quickstarts from JBoss Central won't run properly via Run AS > Run in Server (was: kitchensink-rf doesn't run properly via Run AS > Run in Server)
> Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
> Priority: Critical
>
> 1. Import kitchensink-rf from JBoss Central
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20117) Explorer: new builds get triggered if I'm playing around in OpenShift v3 connection tree
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20117?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-20117:
---------------------------------------
I would venture to say that there is no bug and that something is happening as expected. Builds is something the server is providing support for and is part of the large build/deploy chain in general. I would think if there were a larger issue it would have already been found, especially this close to the 1.0 drop.
> Explorer: new builds get triggered if I'm playing around in OpenShift v3 connection tree
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-20117
> URL: https://issues.jboss.org/browse/JBIDE-20117
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> After I create an application from template and I play around with OpenShift v3 connection (expand tree items, collapse them, refresh resources, connection etc.) there are several builds triggered, what should not be. Currently I do not know what exactly is triggering builds, it's in state of investigating.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20111) kitchensink-rf doesn't run properly via Run AS > Run in Server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20111:
--------------------------------
Priority: Critical (was: Major)
> kitchensink-rf doesn't run properly via Run AS > Run in Server
> --------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
> Priority: Critical
>
> 1. Import kitchensink-rf from JBoss Central
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20111) kitchensink-rf doesn't run properly via Run AS > Run in Server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20111:
-------------------------------------
So this is caused by the examples having an artifactId != folder name, which eclipse doesn't support if installed at the root of the workspace.
A workaround is to create the project in a non default location.
I have a patch ready, that'll unzip examples not directly under the workspace root.
> kitchensink-rf doesn't run properly via Run AS > Run in Server
> --------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
>
> 1. Import kitchensink-rf from JBoss Central
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19946) running webservice test gives errors
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19946?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19946:
------------------------------------
* Try running with JDK 8 instead of 7. 8 is now required if you depend on Base's org.jboss.tools.foundation.core or org.jboss.tools.foundation.core.test.
* Try running with Tycho 0.22 instead of 0.23. 0.23 is the new default in master branch (we used 0.22 in Beta1x).
{code}mvn install -DtychoVersion=0.22.0
mvn install -DtychoVersion=0.23.0{code}
> running webservice test gives errors
> ------------------------------------
>
> Key: JBIDE-19946
> URL: https://issues.jboss.org/browse/JBIDE-19946
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Max Rydahl Andersen
> Assignee: Brian Fitzpatrick
> Fix For: 4.3.0.Beta2
>
>
> running 4.3.0.Beta1x with jdk's defined I get this error:
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> Retrieving document at 'file:/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
> null
> null
> Retrieving document at '/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 272.543 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 82.428 sec
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 127.267 sec <<< FAILURE!
> junit.framework.AssertionFailedError: ***********************
> Create Web Service Client...
> Create Web Service...
> Create Web Service Operation...
> Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
> at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
> at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
> Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
> at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
> at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
> at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
> at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
> at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> ... 4 more
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.checkText(JBossWSJavaFirstCommandTest.java:163)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult(JBossWSJavaFirstCommandTest.java:116)
> testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 15.26 sec
> testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 17.628 sec
> testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 14.25 sec
> testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 9.174 sec
> testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 6.416 sec
> Results :
> Failed tests:
> JBossWSJavaFirstCommandTest.testDeployResult:116->checkText:163 ***********************
> Create Web Service Client...
> Create Web Service...
> Create Web Service Operation...
> Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
> at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
> at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
> Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
> at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
> at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
> at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
> at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
> at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20117) Explorer: new builds get triggered if I'm playing around in OpenShift v3 connection tree
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20117?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20117:
------------------------------------------
[~jcantrill] [~mlabuda] ok so if this is reproducible but not caused by JBoss Tools/openshift-restclient-java then I believe that this should be filed to openshift bugzilla?
> Explorer: new builds get triggered if I'm playing around in OpenShift v3 connection tree
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-20117
> URL: https://issues.jboss.org/browse/JBIDE-20117
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> After I create an application from template and I play around with OpenShift v3 connection (expand tree items, collapse them, refresh resources, connection etc.) there are several builds triggered, what should not be. Currently I do not know what exactly is triggering builds, it's in state of investigating.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20039) Application wizard: templates tree should look disabled when I switch to use templates from local disk (Linux GTK3 only)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20039?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20039:
------------------------------------------
[~snjeza] thanks, this is minor but still good news to know that this is being tracked.
> Application wizard: templates tree should look disabled when I switch to use templates from local disk (Linux GTK3 only)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20039
> URL: https://issues.jboss.org/browse/JBIDE-20039
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: my_wizard_with_disabled_tree.png, templates-tree-no-disabled.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 OpenShift server in explorer
> # EXEC: in Explorer: pick "New"->"Application" from context menu when selecting a project in your connection
> # ASSERT: application wizard pops up, radio "Use a template from server" is preselected
> # EXEC: switch radio "Use a template from my local file system"
> Result:
> There's no visual indication that the tree with server templates is not clickable any more. The "problem" is only visual, the tree is not clickable but doesnt look disabled for me.
> !templates-tree-no-disabled.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20123) StackOverflowError when calling 'Port forwarding...'
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20123?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20123:
-------------------------------------
Priority: Critical (was: Major)
> StackOverflowError when calling 'Port forwarding...'
> ----------------------------------------------------
>
> Key: JBIDE-20123
> URL: https://issues.jboss.org/browse/JBIDE-20123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> The issue happens because StandaloneCartridgeResource.toString()/ApplicationResource.toString() methods from openshift-java-client-2.7.0.Final.jar are called recursively.
> Stacktrace:
> !MESSAGE An internal error occurred during: "Verifying SSH session...".
> !STACK 0
> java.lang.StackOverflowError
> at java.lang.StringBuilder.append(StringBuilder.java:136)
> at sun.util.locale.provider.LocaleResources.getTimeZoneNames(LocaleResources.java:255)
> at sun.util.locale.provider.TimeZoneNameProviderImpl.getDisplayNameArray(TimeZoneNameProviderImpl.java:122)
> at sun.util.locale.provider.TimeZoneNameProviderImpl.getDisplayName(TimeZoneNameProviderImpl.java:98)
> at sun.util.locale.provider.TimeZoneNameUtility$TimeZoneNameGetter.getName(TimeZoneNameUtility.java:328)
> at sun.util.locale.provider.TimeZoneNameUtility$TimeZoneNameGetter.getObject(TimeZoneNameUtility.java:281)
> at sun.util.locale.provider.TimeZoneNameUtility$TimeZoneNameGetter.getObject(TimeZoneNameUtility.java:267)
> at sun.util.locale.provider.LocaleServiceProviderPool.getLocalizedObjectImpl(LocaleServiceProviderPool.java:281)
> at sun.util.locale.provider.LocaleServiceProviderPool.getLocalizedObject(LocaleServiceProviderPool.java:265)
> at sun.util.locale.provider.TimeZoneNameUtility.retrieveDisplayName(TimeZoneNameUtility.java:135)
> at java.util.TimeZone.getDisplayName(TimeZone.java:400)
> at java.util.Date.toString(Date.java:1045)
> at java.lang.String.valueOf(String.java:2982)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at com.openshift.internal.client.ApplicationResource.toString(ApplicationResource.java:1015)
> at java.lang.String.valueOf(String.java:2982)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at com.openshift.internal.client.StandaloneCartridgeResource.toString(StandaloneCartridgeResource.java:174)
> at java.lang.String.valueOf(String.java:2982)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at com.openshift.internal.client.ApplicationResource.toString(ApplicationResource.java:1015)
> at java.lang.String.valueOf(String.java:2982)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at com.openshift.internal.client.StandaloneCartridgeResource.toString(StandaloneCartridgeResource.java:174)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20123) StackOverflowError when calling 'Port forwarding...'
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20123?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20123:
-------------------------------------
Priority: Major (was: Critical)
> StackOverflowError when calling 'Port forwarding...'
> ----------------------------------------------------
>
> Key: JBIDE-20123
> URL: https://issues.jboss.org/browse/JBIDE-20123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta2
>
>
> The issue happens because StandaloneCartridgeResource.toString()/ApplicationResource.toString() methods from openshift-java-client-2.7.0.Final.jar are called recursively.
> Stacktrace:
> !MESSAGE An internal error occurred during: "Verifying SSH session...".
> !STACK 0
> java.lang.StackOverflowError
> at java.lang.StringBuilder.append(StringBuilder.java:136)
> at sun.util.locale.provider.LocaleResources.getTimeZoneNames(LocaleResources.java:255)
> at sun.util.locale.provider.TimeZoneNameProviderImpl.getDisplayNameArray(TimeZoneNameProviderImpl.java:122)
> at sun.util.locale.provider.TimeZoneNameProviderImpl.getDisplayName(TimeZoneNameProviderImpl.java:98)
> at sun.util.locale.provider.TimeZoneNameUtility$TimeZoneNameGetter.getName(TimeZoneNameUtility.java:328)
> at sun.util.locale.provider.TimeZoneNameUtility$TimeZoneNameGetter.getObject(TimeZoneNameUtility.java:281)
> at sun.util.locale.provider.TimeZoneNameUtility$TimeZoneNameGetter.getObject(TimeZoneNameUtility.java:267)
> at sun.util.locale.provider.LocaleServiceProviderPool.getLocalizedObjectImpl(LocaleServiceProviderPool.java:281)
> at sun.util.locale.provider.LocaleServiceProviderPool.getLocalizedObject(LocaleServiceProviderPool.java:265)
> at sun.util.locale.provider.TimeZoneNameUtility.retrieveDisplayName(TimeZoneNameUtility.java:135)
> at java.util.TimeZone.getDisplayName(TimeZone.java:400)
> at java.util.Date.toString(Date.java:1045)
> at java.lang.String.valueOf(String.java:2982)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at com.openshift.internal.client.ApplicationResource.toString(ApplicationResource.java:1015)
> at java.lang.String.valueOf(String.java:2982)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at com.openshift.internal.client.StandaloneCartridgeResource.toString(StandaloneCartridgeResource.java:174)
> at java.lang.String.valueOf(String.java:2982)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at com.openshift.internal.client.ApplicationResource.toString(ApplicationResource.java:1015)
> at java.lang.String.valueOf(String.java:2982)
> at java.lang.StringBuilder.append(StringBuilder.java:131)
> at com.openshift.internal.client.StandaloneCartridgeResource.toString(StandaloneCartridgeResource.java:174)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20014) Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20014?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20014:
------------------------------------------
great news that you found the problem, thx!
Unfortunately this wont get fixed before SR1 :(
> Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-20014
> URL: https://issues.jboss.org/browse/JBIDE-20014
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.0.Beta1
> Environment: Linux GTK2, GTK3
> Reporter: Andre Dietisheim
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
> Attachments: new-submenu-not-visible.png, new-submenu-visible.png
>
>
> It is quite frequent that the "New" (and "Show in" for v3) submenu wont show up. This happens even if the submenu is first visible but then, on a 2nd context menu invocation, disappears
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months