There is a bug in this version of synapse that causes a segfault when used with xim. See these reports: - https://bugs.launchpad.net/synapse-project/+bug/1401909 - https://bugs.launchpad.net/synapse-project/+bug/1219314 This should most certainly not be the stable version of synapse. https://bugs.gentoo.org/show_bug.cgi?id=563924 Reproducible: Always Steps to Reproduce: 1. Start synapse 2. Type a letter Actual Results: Synapse crashes Expected Results: Synapse searches programs
@gnome, the upstream report suggest to start with GTK_IM_MODULE='' synapse as a workaround. What do you think? BTW, I am heavily using this and never had any problems.
I tried the workaround and it works. However, it has the nasty side effect that my custom .XCompose file isn't used in programs spawned using synapse. Which is pretty annoying. Furthermore, I'm not sure what causes the bug. It might be that I'm not using a very basic X setup, with Awesome WM as my window manager.
I am using it on a full blown GNOME3 setup and on XFCE.
(In reply to Justin Lecher from comment #1) > @gnome, > > the upstream report suggest to start with > > GTK_IM_MODULE='' synapse > > as a workaround. What do you think? > > BTW, I am heavily using this and never had any problems. Do you mean by using it only for synapse or setting that globally with an environment file? I would disagree with that last approach, well, at least, we would need to investigate more about what values can that variable have and how could it interact with other programs :/
No, of course not global, just for synapse. So far upstream has no clue what is going on and I personally never saw it. So it would be a workaround until it has been investigated properly.
Well, only for synapse I wouldn't see any problem. I see that bug also occurs on other distributions and the same workaround is suggested. Maybe it would be interesting to know what module is causing this problem :/ I have this: $ ls -l /usr/lib/gtk-3.0/3.0.0/immodules/ total 228 -rwxr-xr-x 1 root root 23552 sep 20 20:25 im-am-et.so -rwxr-xr-x 1 root root 10320 sep 20 20:25 im-cedilla.so -rwxr-xr-x 1 root root 11864 sep 20 20:25 im-cyrillic-translit.so -rwxr-xr-x 1 root root 31568 sep 5 09:59 im-ibus.so -rwxr-xr-x 1 root root 12288 sep 20 20:25 im-inuktitut.so -rwxr-xr-x 1 root root 10960 sep 20 20:25 im-ipa.so -rwxr-xr-x 1 root root 14560 sep 20 20:25 im-multipress.so -rwxr-xr-x 1 root root 14400 sep 20 20:25 im-thai.so -rwxr-xr-x 1 root root 23536 sep 20 20:25 im-ti-er.so -rwxr-xr-x 1 root root 23536 sep 20 20:25 im-ti-et.so -rwxr-xr-x 1 root root 12184 sep 20 20:25 im-viqr.so -rwxr-xr-x 1 root root 31432 sep 20 20:25 im-xim.so I think ibus was preferred but I am unsure now :/
With that list of immodules, it works for me without any workaround
ls -l /usr/lib/gtk-3.0/3.0.0/immodules/ total 200 -rwxr-xr-x 1 root root 23616 Sep 21 09:45 im-am-et.so* -rwxr-xr-x 1 root root 10384 Sep 21 09:45 im-cedilla.so* -rwxr-xr-x 1 root root 11928 Sep 21 09:45 im-cyrillic-translit.so* -rwxr-xr-x 1 root root 12352 Sep 21 09:45 im-inuktitut.so* -rwxr-xr-x 1 root root 11024 Sep 21 09:45 im-ipa.so* -rwxr-xr-x 1 root root 14560 Sep 21 09:45 im-multipress.so* -rwxr-xr-x 1 root root 14400 Sep 21 09:45 im-thai.so* -rwxr-xr-x 1 root root 23600 Sep 21 09:45 im-ti-er.so* -rwxr-xr-x 1 root root 23600 Sep 21 09:45 im-ti-et.so* -rwxr-xr-x 1 root root 12248 Sep 21 09:45 im-viqr.so* -rwxr-xr-x 1 root root 31432 Sep 21 09:45 im-xim.so* I also tried to install ibus, but it didn't crash.
I forgot to comment back to this. The workaround works, but as I said it ignores my custom .XCompose file in any program that is spawned by synapse. The immodules I have installed are these: $ ls -l /usr/lib/gtk-3.0/3.0.0/immodules/ total 164 -rwxr-xr-x 1 root root 19416 4 jan 21:57 im-am-et.so* -rwxr-xr-x 1 root root 6184 4 jan 21:57 im-cedilla.so* -rwxr-xr-x 1 root root 7720 4 jan 21:57 im-cyrillic-translit.so* -rwxr-xr-x 1 root root 8152 4 jan 21:57 im-inuktitut.so* -rwxr-xr-x 1 root root 6832 4 jan 21:57 im-ipa.so* -rwxr-xr-x 1 root root 14456 4 jan 21:57 im-multipress.so* -rwxr-xr-x 1 root root 14296 4 jan 21:57 im-thai.so* -rwxr-xr-x 1 root root 19400 4 jan 21:57 im-ti-er.so* -rwxr-xr-x 1 root root 19400 4 jan 21:57 im-ti-et.so* -rwxr-xr-x 1 root root 8048 4 jan 21:57 im-viqr.so* -rwxr-xr-x 1 root root 31336 4 jan 21:57 im-xim.so* Why was the old ebuild removed from th tree? That one was not causing problems for me and this one has a bug that makes it unusable. Could the old version be added back to the tree until this issue is resolved upstream?
[0] says it was fixed on 4 February 2018, and that was when 0.2.99.3 was released. 0.2.99.4 is in the tree now. [0] https://bugs.launchpad.net/synapse-project/+bug/1219314
