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.

Sign up for GitHub

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

Jump to bottom

Ubuntu issue #1242 from bitcoin (qt menus disappearing) #16

Closed
caraka opened this issue Jan 13, 2015 · 1 comment
Closed

Ubuntu issue #1242 from bitcoin (qt menus disappearing) #16

caraka opened this issue Jan 13, 2015 · 1 comment

Comments

@caraka
Copy link
Member

caraka commented Jan 13, 2015

Kia ora Rob
I thought I was packaging poorly, but it turns out that there is a qt issue with Unity and thus most Ubuntu users. While the original issue raised cites Ubuntu 1204, I can confirm that it affects the Unity desktop in 1404-1504. laanwj at bitcoin has already resolved it. the issue was raised here:
bitcoin/bitcoin#1242
The issue was resolved with the commits here:
bitcoin/bitcoin#3493
Let me know if this is something you can work on in the near term, or if I should attempt to use laanwj's commits as a patch in my builds. I'd rather not mess around under the hood, to be honest. I'm neither a c or a qt programmer, and besides, the whole idea with packaging is to keep the trust by using the upstream code for the builds and only tweaking at the edges.
Cheers
Rick (caraka)
@caraka
Copy link
Member Author

caraka commented Nov 8, 2015

Threads split and issue resolved with release 3.5.2.x

@caraka caraka closed this as completed Nov 8, 2015
@jamescowens jamescowens mentioned this issue Oct 31, 2019
Merged
div72 referenced this issue in div72/Gridcoin-Research Aug 12, 2020
@laanwj
Handle UTF-8
c9a716c 
This adds full UTF-8 support both on input and output.

Input: read and validate full UTF-8, both Basic Multilingual Plane
and extended characters.
Collate surrogate pairs as specified in RFC4627.
This ensures that UTF-8 strings that reach the application are
always valid, and that invalid UTF-8 fails parsing.

Output: Assume UTF-8 strings provided for output are valid.
The escaping was broken, fix this by not encoding UTF-8 characters with \u.
Writing them to the output stream as-is is the right thing to do.
See https://www.ietf.org/rfc/rfc4627.txt:

    "JSON text SHALL be encoded in Unicode.  The default encoding is UTF-8."

Also add tests for the new functionality.
Fixes #16.
div72 referenced this issue in div72/Gridcoin-Research Aug 12, 2020
@pwnall @cmumford
Improved configuration for YouCompleteMe, Travis and AppVeyor. (#16)
bca495f 
This change updates the .ycm_extra_conf.py implementation with a cleaned
up version that has more comments and passes Google's pylint rules, and
adds a missing include path to .clang_complete.

This change also switches the recommended CMake build directory from
out/ to build/. While the former is shorter and thus more convenient,
the later has emerged as a standard and has better tools support.

Last, this change removes the Visual Studio 2015 bots from the AppVeyor
configuration. We generally only support the Windows compilers used to
build Chromium.
@jamescowens jamescowens mentioned this issue Jul 16, 2021
Closed
This was referenced Oct 23, 2022
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@caraka