Le samedi 12 janvier 2019 à 11:40 +0100, Pavel Sanda a écrit : > On Sat, Jan 12, 2019 at 11:08:16AM +0100, Daniel CLEMENT wrote: > > > So, not specifcally LyX issue... You could try to post bug in > > > debian > > > or even with qt... > > > > After some searching, it looks like the bug is already known. > > > > I came across this thread: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=477552 > > > > which (following comment #7) lead me to this workaround: I added > > > > export QT_IM_MODULE=xim > > > > to my .xsessionrc file > > Interesting, that shouldn't matter in Qt5. Is it that you still use > Qt4 in your config?
No, in Debian 9 it's basically Qt5 everywhere (though I do have some Qt4-related packages installed, e.g. python.qt4) > My problem is with Qt5. > > > It "works", but frankly, I'd rather not have to do that... > > Agreed, this is just wrong list to ask for the fix, the problem is > either > in the config of X/DM or Qt code and it might be difficult to spot > who is > actually responsible for the problem... > Pavel I do understand that. Yet, I can't help thinking there's something "special" with the LyX main edit window. I mean, I have several other Qt apps (Filezilla, Scribus, Clementine...)--though I don't use them half as much as LyX. None of them has this problem. Even in LyX, the dead keys do work well within the dialogs (e.g. file-save as). It's only the main window that shows the problem. Moreover, I could check that the dead keys did work properly within LyX just freshly installed in a live-USB session. I'm puzzled. As long as my workaround works, all is well... but if it fails eventually, I'll be in trouble. -- Daniel CLEMENT
