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

GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted. #258

Closed
streamofstars opened this issue Mar 26, 2021 · 2 comments · Fixed by #277
Closed
Labels
Bug Something isn't working macOS

Comments

@streamofstars
Copy link

Right-mouse-button clicking on any transaction in Transactions tab and copying address, label, and so on, results in the following message in the debug.log:

GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.

The copied content is actually getting copied to the clipboard, so no problem with the feature itself, just with the log getting filled with unnecessary messages. I don't know if the issue was present in previous versions or if it's system specific, just noticed that today when I was observing debug.log live when submitting a new transaction.

Bitcoin Core v0.21.0
MacOS 11.2.3

@streamofstars streamofstars changed the title Any report, issue or feature request related to the GUI should be reported at https://github.com/bitcoin-core/gui/issues/ GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted. Mar 26, 2021
@hebasto
Copy link
Member

hebasto commented Mar 26, 2021

Also see bitcoin/bitcoin#7628 (comment)

@hebasto
Copy link
Member

hebasto commented Apr 10, 2021

@streamofstars

Do you mind testing #277?

@hebasto hebasto added the Bug Something isn't working label Apr 10, 2021
@bitcoin-core bitcoin-core locked as resolved and limited conversation to collaborators Aug 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Something isn't working macOS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants