Comment #4 on issue 1629 by [email protected]: Segmentation fault with
ibus-table IPA-X-Sampa
http://code.google.com/p/ibus/issues/detail?id=1629
You can get some more debug output by editing
/usr/libexec/ibus-engine-table,
that file contains:
# Set this variable to something > 0 to get more debug output.
# (Debug output may show up in the log file and/or in the lookup table):
# export IBUS_TABLE_DEBUG_LEVEL=1
you can remove the comment character before "export
IBUS_TABLE_DEBUG_LEVEL=1"
The debug output goes to ~/.ibus/tables/debug.log, you do not need to run it
manually to find the debug output there. I usually just run
tail -F ~/.ibus/tables/debug.log
in some terminal to see the debug output while experimenting with
ibus-table.
What version of ibus-table are you using?
ibus-table >= 1.8.0 requires Python3!
How is ibus-table started in /usr/libexec/ibus-engine-table?
It should contain a line like:
exec /usr/bin/python3 ${prefix}/share/ibus-table/engine/main.py $@
and the python interpreter used there should be Python3
(i.e. on Arch Linux this could be /usr/bin/python).
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message because you are subscribed to the Google
Groups "ibus-devel" group.
iBus project web page: http://code.google.com/p/ibus/
iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
---
You received this message because you are subscribed to the Google Groups "ibus-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
