Error while trying to upload screen shot to Jira

Description

with the latest version 1.2.9 I started experiencing problem when trying to upload screenshots to Jira via, otherwise, extremely helpful and super cool Jira plugin. With the same rig and with the previous version of Greenshot I had not a single problem. The address of the jira server is verified, connectivity and availability of the service is verified. As I said it used to work just fine before.
steps to reproduce:
1. take a screenshot.
2. Open it in the greenshot editor
3. click on the "Uplod to Jira" button.
And I receive the following error message with the consecutive dump:

Software version: 1.2.9.112-RELEASE-9bc62ac42bd37d7ba2b19946b70d40a599332b75 (64 bit) .NET runtime version: 4.0.30319.42000+ Time: 2017-01-13 11:02:08 +02:00 OS: unknown (x64) 10.0 build 14393 revision 0 GDI object count: 153 User object count: 140 Exception: System.NotSupportedException Message: Unsupported result type Bitmap & text/html combination. Stack: at Dapplo.HttpExtensions.HttpResponseMessageExtensions.<GetAsAsync>d__1`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Dapplo.HttpExtensions.HttpClientExtensions.<GetAsAsync>d__4`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Dapplo.HttpExtensions.UriActionExtensions.<GetAsAsync>d__3`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Dapplo.Jira.JiraApi.<GetUriContentAsync>d__18`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GreenshotJiraPlugin.IssueTypeBitmapCache.<CreateAsync>d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GreenshotJiraPlugin.AsyncMemoryCache`2.<>c__DisplayClass26_0.<<GetOrCreateInternalAsync>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GreenshotJiraPlugin.AsyncMemoryCache`2.<GetOrCreateInternalAsync>d__26.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GreenshotJiraPlugin.JiraConnector.<GetIssueTypeBitmapAsync>d__30.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GreenshotJiraPlugin.Forms.JiraForm.<JiraFilterBox_SelectedIndexChanged>d__13.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state) Configuration dump:

Environment

Windows 10 build 1607 x64, Intel core i5-u4300

Attachments

1
  • 13 Jan 2017, 05:54 PM

Gliffy Diagrams

Activity

Show:

Robin Krom January 25, 2017 at 6:18 PM

The release will come in ~ a week.

Robin Krom January 25, 2017 at 6:17 PM
Edited

According to https://greenshot.atlassian.net/browse/BUG-2122#icft=BUG-2122 this was fixed with hhttps://github.com/greenshot/greenshot/releases/tag/Greenshot-UNSTABLE-1.2.9.124 (1.2.9.123 or later)

Closing this ticket, as you didn't respond anymore.

Robin Krom January 25, 2017 at 7:32 AM

I would really like to solve this issue, so I was hoping you can help us here.

Yesterday I made a newer version of Greenshot which should give more information in the log, without changing the log level.
https://github.com/greenshot/greenshot/releases/tag/Greenshot-UNSTABLE-1.2.9.120

Might there, by any chance, be one of the following characters:

{}

in your filename? This was tested with the JIRA version I am using, but maybe the older one doesn't escape the information correctly.

Robin Krom January 18, 2017 at 9:52 AM

Did you manage to have a look at this?

Robin Krom January 16, 2017 at 10:09 AM

According to the error, the "attach" operation itself went wrong. In fact, it says that the answer it got from your JIRA server is not valid (invalid JSON string).

As far as I was able to find out in Atlassians documentation, for the "attach" operation there is no difference for the API between your v6.1.3 and my "old" test system 6.2.7. So the error from that point of view doesn't make sense, I cannot reproduce the error, for me it works just fine.

I hope you are able to support me a bit, so we can solve this?

Unfortunately I cannot see what happened, it might be that there is some kind of error which isn't detected correctly.
In theory there are some possibilities:

  1. Filename has a format which is not supported?

  2. You don't have the rights to attacht to the JIRA ID (still need to work on that)

  3. Different errors...

We might be able to see what is going on, if you do the following:

  1. Stop Greenshot

  2. edit the log4net.xml file in the Greenshot installation directory, change

    <level value="INFO" />

    to

    <level value="DEBUG" />
  3. Start Greenshot again

Now try again, and afterwards have a look in the greenshot.log (http://getgreenshot.org/faq/where-can-i-find-greenshots-log-file/)
There should be a bit more information, although it writes the response of the server limited to a certain length...

Don't forget to change the log level back to INFO, otherwise Greenshot will write quite a lot into it's file.

Fixed

Details

Assignee

Reporter

Affects versions

Components

Priority

Time tracking

2h logged

Sprint

Created January 13, 2017 at 9:19 AM
Updated January 26, 2017 at 8:24 AM
Resolved January 13, 2017 at 7:11 PM