Bug 1649858 - using <ctrl><shift>u to enter unicode no longer works.
Summary: using <ctrl><shift>u to enter unicode no longer works.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 28
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: fujiwara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-14 16:21 UTC by Patrick
Modified: 2018-11-15 09:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-15 03:04:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Patrick 2018-11-14 16:21:29 UTC
Description of problem:
For years I've been able to type <ctrl><shift>u to enter unicode input mode and type the hex value of a unicode character. Now it does nothing.

How reproducible:
While in an application that lets you enter text press <ctrl><shift>u226c followed by a space

Actual results:
Nothing

Expected results:
Output of two notes

Additional info:
Please don't say use <ctrl><shift>e for the emoji chooser. It can not substitute for the missing behavior. It's a chooser not an inline input method.

For some reason the emoji chooser HAS unicode but it's horrible! It's also weird. Why is unicode in an emoji chooser? Who would want to use that? It takes you off to a different window which disappears randomly behind the input screen while you're trying to use it. Whoever created it seems to have no experience with usability. I'm a software engineer with decades of experience and we had to take classes in usability in college. Don't they teach that anymore? 

I have to select unicode from a list and then search for the unicode character I already know the code point for. It's pretty ghastly. Then when I find it and select it the creepy window doesn't even go away!!! Whoever created it seems really proud of it and just wants it to stay around.

Comment 1 fujiwara 2018-11-15 03:04:32 UTC
Try the latest ibus under updates-testing.

Comment 2 Patrick 2018-11-15 09:36:21 UTC
Thank you fujiwara. I can confirm that the behavior has returned to normal. You're the best:)


Note You need to log in before you can comment on or make changes to this bug.