From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ibus failed to insert character through unicode or insert emoji
Date: Mon, 01 May 2023 05:48:20 +0200 [thread overview]
Message-ID: <20230501034820.saJ4qduGNaiSS596uRflYgooDdSUqntzH8ytr1exR-A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43536@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3295 bytes --]
Closed issue by funk443 on void-packages repository
https://github.com/void-linux/void-packages/issues/43536
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.21_1 x86_64 AuthenticAMD notuptodate rFFFFF
### Package(s) Affected
ibus-1.5.28_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Probably related to this:
https://github.com/ibus/ibus/issues/2476
### Expected behaviour
After pressing the keybinding for inserting a char using unicode, enter `0041` should output `A`.
Or after pressing the keybinding for inserting a emoji, enter `smile` and press space bar should output `😊`.
### Actual behaviour
Nothing was outputted.
The output from ibus-daemon:
```
(ibus-ui-gtk3:30847): IBUS-WARNING **: 11:12:55.699: panel.vala:307: XDG_CURRENT_DESKTOP is not exported in your desktop session.
(ibus-ui-gtk3:30847): IBUS-WARNING **: 11:12:55.699: panel.vala:310: If you launch KDE5 on xterm, export XDG_CURRENT_DESKTOP=KDE before launch KDE5.
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.784: ibus_serializable_deserialize_object: assertion 'g_type_is_a (type, IBUS_TYPE_SERIALIZABLE)' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.784: ibus_serializable_deserialize_object: assertion 'g_type_is_a (type, IBUS_TYPE_SERIALIZABLE)' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.784: ibus_serializable_deserialize_object: assertion 'g_type_is_a (type, IBUS_TYPE_SERIALIZABLE)' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.784: ibus_serializable_deserialize_object: assertion 'g_type_is_a (type, IBUS_TYPE_SERIALIZABLE)' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.784: ibus_serializable_deserialize_object: assertion 'g_type_is_a (type, IBUS_TYPE_SERIALIZABLE)' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.784: ibus_serializable_deserialize_object: assertion 'g_type_is_a (type, IBUS_TYPE_SERIALIZABLE)' failed
;; Omitted many lines of exact same errors
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.871: ibus_emojier_update_emoji_to_data_dict: assertion 'data != NULL' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.871: ibus_emojier_update_annotation_to_emojis_dict: assertion 'data != NULL' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.871: ibus_emojier_update_category_to_emojis_dict: assertion 'data != NULL' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.871: ibus_emojier_update_emoji_to_data_dict: assertion 'data != NULL' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.871: ibus_emojier_update_annotation_to_emojis_dict: assertion 'data != NULL' failed
(ibus-extension-gtk3:30848): IBUS-CRITICAL **: 11:12:55.871: ibus_emojier_update_category_to_emojis_dict: assertion 'data != NULL' failed
;; Omitted many lines of this alternating pattern of these three errors
```
### Steps to reproduce
1. Start ibus-daemon (using `ibus-daemon -vrxR`)
2. Switch to unicode input mode (default keybinding is `Ctrl-Shift-u`
3. Enter `0041` then press `Space`
4. Switch to emoji input mode (default keybinding is `Super-.`)
5. Enter `smile` then press `Space`
prev parent reply other threads:[~2023-05-01 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 3:17 [ISSUE] " funk443
2023-04-20 6:41 ` oreo639
2023-05-01 3:34 ` fujiwarat
2023-05-01 3:48 ` classabbyamp
2023-05-01 3:48 ` classabbyamp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230501034820.saJ4qduGNaiSS596uRflYgooDdSUqntzH8ytr1exR-A@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).