Open razi006 opened 3 years ago
sarim
commented
3 years ago There is an similar known issue (#156 ) but its rare and no where as close to "crashing nearly once in every line!".
Run ibus-daemon -xrv in a terminal then type bangla as you normally would. When a crash occurs copy the whole output shown in terminal. Try to capture several crash event log this way and upload it here. It'd be really helpful to understand what's going on :)
razi006
commented
3 years ago 
iBus suddenly stops working while typing. I would have to close iBus and start it again! It happened thrice within 5 minutes!
razi006
commented
3 years ago 
Again. Twice in the previous line!
archisman-panigrahi
commented
3 years ago @razi006 As Sarim mentioned, run ibus-daemon -xrv in a terminal, and post the error log. Without it, the issue cannot be analyzed.
archisman-panigrahi
commented
3 years ago Is this the error log during such a crash? We need the error log when ibus crashes.
Keep this thing open, and write Bangla, and wait until it crashes. Then post the error message as text (not as an image).
archisman-panigrahi
commented
3 years ago You did not upload any screenshot. Please copy and paste the terminal outputs as texts instead of images.
razi006
commented
3 years ago (gjs:31207): Gjs-CRITICAL **: 23:34:55.292: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:31207): Gjs-CRITICAL **: 23:34:55.292: The offending signal was create-engine on IBusFactory 0x55f0af129350. == Stack trace for context 0x55f0aeeec1a0 ==
(gjs:31207): IBUS-CRITICAL **: 23:34:55.292: ibus_factory_real_create_engine: assertion 'engine_type != G_TYPE_INVALID' failed
(ibus-ui-gtk3:31035): IBUS-WARNING **: 23:34:55.294: ibus_bus_call_sync: org.freedesktop.IBus.SetGlobalEngine: GDBus.Error:org.freedesktop.DBus.Error.Failed: Set global engine failed: GDBus.Error:org.freedesktop.DBus.Error.Failed: Cannot find engine ibus-avro
(ibus-ui-gtk3:31035): IBUS-WARNING **: 23:34:55.294: panel.vala:818: Switch engine to ibus-avro failed.
ahmed-kaif
commented
3 years ago I am aslo facing the same issue in POP os 21.04:
Here's the output from ibus-daemon -xrv :
(gjs:9008): Gjs-CRITICAL **: 13:09:40.372: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9008): Gjs-CRITICAL **: 13:09:40.372: The offending signal was focus-out on IBusEngine 0x5603f1ae30c0. == Stack trace for context 0x5603f17a01c0 ==
My OS information:
NAME="Pop!_OS"
VERSION="21.04"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.04"
VERSION_ID="21.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
LOGO=distributor-logo-pop-os
needyamin
commented
3 years ago Is there any update? I have same problem in my Linux Mint 20.1 Cinnamon OS
abkarim
commented
2 years ago My texts is আমি চাই যে এই সমa
Here is the terminal message
65288 14 0
65288 14 1073741824
97 30 0
109 50 0
105 23 0
97 30 1073741824
109 50 1073741824
105 23 1073741824
32 57 0
32 57 1073741824
99 46 0
104 35 0
99 46 1073741824
104 35 1073741824
97 30 0
105 23 0
97 30 1073741824
105 23 1073741824
32 57 0
(gjs:9617): Gjs-CRITICAL **: 19:51:51.807: JS ERROR: Gio.IOErrorEnum: Error opening file “/home/karim/.candidate-selections.json”: File exists
_saveCandidateSelectionsToFile/<@/usr/share/ibus-avro/suggestionbuilder.js:423:50
@/usr/share/ibus-avro/main-gjs.js:422:10
32 57 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
99 46 0
99 46 1073741824
97 30 0
105 23 0
97 30 1073741824
32 57 0
(gjs:9617): Gjs-CRITICAL **: 19:51:54.211: JS ERROR: Gio.IOErrorEnum: Error opening file “/home/karim/.candidate-selections.json”: File exists
_saveCandidateSelectionsToFile/<@/usr/share/ibus-avro/suggestionbuilder.js:423:50
@/usr/share/ibus-avro/main-gjs.js:422:10
105 23 1073741824
32 57 1073741824
122 44 0
122 44 1073741824
101 18 0
101 18 1073741824
32 57 0
32 57 1073741824
101 18 0
105 23 0
101 18 1073741824
32 57 0
105 23 1073741824
32 57 1073741824
115 31 0
115 31 1073741824
111 24 0
111 24 1073741824
109 50 0
109 50 1073741824
109 50 0
109 50 1073741824
65288 14 0
65288 14 1073741824
111 24 0
111 24 1073741824
109 50 0
115 31 0
109 50 1073741824
115 31 1073741824
115 31 0
115 31 1073741824
97 30 0
97 30 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
115 31 0
115 31 1073741824
115 31 0
115 31 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
(ibus-ui-gtk3:9584): Gtk-WARNING **: 19:52:07.019: no trigger event for menu popup
115 31 0
115 31 1073741824
65288 14 0
65288 14 1073741824
115 31 0
115 31 1073741824
121 21 0
121 21 1073741824
115 31 0
115 31 1073741824
97 30 0
(gjs:9617): Gjs-CRITICAL **: 19:52:13.897: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:13.898: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.440: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.440: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.448: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.448: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.450: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.450: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.451: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.451: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.452: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.452: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.454: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.454: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.455: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.455: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.456: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.456: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.457: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.457: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:14.566: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:14.566: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:16.133: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:16.133: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:16.249: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:16.249: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:16.430: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:16.430: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:16.491: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:16.491: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:16.760: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:16.760: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:16.899: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:16.899: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.020: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.021: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.062: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.062: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.411: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.411: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.426: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.426: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.431: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.431: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.434: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.435: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.437: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.437: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.485: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.485: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.574: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.574: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.587: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.588: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.592: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.592: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.595: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.595: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.595: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.595: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.666: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.667: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.753: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.753: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.766: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.766: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.770: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.770: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.772: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.773: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.775: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.775: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:17.853: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:17.854: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:19.061: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:19.061: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:19.065: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:19.066: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:19.070: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:19.070: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:19.071: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:19.071: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:19.074: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:19.074: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:19.075: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:19.075: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:42.009: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:42.009: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:42.010: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:42.010: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:42.022: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:42.022: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:42.026: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:42.026: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:42.027: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:42.027: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:42.027: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:42.027: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:42.028: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:42.028: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:52:42.029: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:52:42.029: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:05.966: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:05.966: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:05.966: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:05.966: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:08.031: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:08.031: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:08.037: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:08.037: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:08.045: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:08.045: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:08.048: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:08.048: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:08.051: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:08.051: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:08.052: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:08.052: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:21.637: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:21.637: The offending signal was focus-out on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:21.638: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:21.639: The offending signal was focus-in on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:21.639: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:21.639: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:21.820: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:21.820: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:21.917: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:21.918: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
(gjs:9617): Gjs-CRITICAL **: 19:53:22.201: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
(gjs:9617): Gjs-CRITICAL **: 19:53:22.202: The offending signal was process-key-event on IBusEngine 0x55e5bff6e8b0.
== Stack trace for context 0x55e5bf3921a0 ==
#0 55e5bf3b5570 i /usr/share/ibus-avro/main-gjs.js:422 (177d712846a0 @ 1506)
@abkarim Your issue is #156.
abkarim
commented
2 years ago @sarim I followed the process and it's not crashing much as the previously does. But now I figured out that If I try to write slightly fast it crashes. But although I'm not sure about it, just mentioned it here to help you figure out the problem. Thank you
gunnarhj
commented
2 years ago @abkarim Your issue is #156.
@sarim: Please note that 276fcafa is not yet in the ibus-avro package in Debian/Ubuntu. Is there a reason to reconsider that and with that make the Debian/Ubuntu package equal to this repo?
I'm using Linux Mint 20.2 Cinnamon which is based on Ubuntu 20.04 focal. While I'm typing in Bangla, iBus-avro is crashing nearly once in every line! When it happens, I need to restart iBus each time! Is there any solution for that? I've downloaded iBus-avro from Synaptic Package Manager.