Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QT] When viewing a transaction's details, the "From" field always says "unknown" #49

Open
jacobbaratta opened this issue Feb 17, 2018 · 0 comments

Comments

@jacobbaratta
Copy link

Describe the issue

In the QT client, when you double-click on a transaction or right click on it and select "show transaction details", a window appears with the transaction details in it. In this window, the "From" field always displays "unknown" instead of the expected source address(es) for the transaction.

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

  1. Open garlicoin-qt
  2. Navigate to the "Transactions" tab
  3. Double-click on a transaction or right click on it and select "show transaction details"

Expected behaviour

The "From" field should display the source address(es) for the transaction (unless the transaction source is new coins, in which case it should either display something like "new coins" or "unknown").

Actual behaviour

The "From" field will display "unknown" instead of the expected source address(es).

Screenshots.

screen shot 2018-02-16 at 7 23 18 pm

(for the above transaction, you can see in the explorer that the correct source address should be "GJ5ukdQRqVbVNftEYw4ZnRN5DxhBKdfEtZ", not "unknown")

What version of garlicoin-core are you using?

v0.16.0.2-0787900-dirty (64-bit) — Self compiled from GitHub source code.

Note: This bug was also observed on a pre-allium version of garlicoin-qt.

Machine specs:

  • OS: OSX (macOS) 10.12.6
  • CPU: i7-3770k
  • RAM: 24 GB
  • Disk size: 500 GB (OSX boot disk)
  • Disk Type (HD/SDD): SSD (OSX boot disk)

Note: This is a Hackintosh, not a genuine Apple computer. I have not tested to see if this issue exists on genuine Apple computers or on other operating systems, but there is no reason to suspect that it would not be present on genuine Apple computers or on other operating systems, and therefore I decided not to test for this bug on other platforms.

Any extra information that might be useful in the debugging process.

N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant