On Monday, 4 September 2017 05:19:18 -03 René J. V. Bertin wrote:
> That bug report suggests only Qt performance is affected. But if I'm not
> mistaken, Linux accessibility goes through the d-bus, and if that daemon is
> being flooded other applications can suffer as well (cf. KMail4
>
And one more thing: I haven't been seeing the issue I reported originally since
getting rid of the ibus stuff as described earlier in this thread. Uninstalling
at-spi2-core must have been the real fix as I installed ibus in one of my
attempts to get a grip on the issue.
René J. V. Bertin wrote:
>> QT_LINUX_ACCESSIBILITY_ALWAYS_ON
>
> Interesting, I have no trace of that variable, and I cannot imagine that
> uninstalling at-spi2-core would have unset it in all running shells.
In addition, the code only checks if this variable is set. You cannot do
El 12 jun. 2017 5:09 a.m., "Allan Sandfeld Jensen"
escribió:
On Montag, 12. Juni 2017 09:49:43 CEST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > Check your environment. You must have something that tells Qt to use it.
>
> For Qt4 there's QT4_IM_MODULE indeed, and you
On sábado, 2 de septiembre de 2017 10:51:08 -03 you wrote:
[snip]
> > QT_LINUX_ACCESSIBILITY_ALWAYS_ON
> >
> > It forces Qt to send accessibility events with new content trees
> > everything
> > something changes.
> >
> > Though the real problem might be that Linux lacks a good way to enable
> >
On lunes, 12 de junio de 2017 10:32:17 -03 Allan Sandfeld Jensen wrote:
> On Montag, 12. Juni 2017 10:17:50 CEST René J. V. Bertin wrote:
> > Allan Sandfeld Jensen wrote:
> > > I am on Debian and found the same thing. Apt-get remove im-config solves
> > > the issue. Apparently it is a buggy
Allan Sandfeld Jensen wrote:
> QT_LINUX_ACCESSIBILITY_ALWAYS_ON
Interesting, I have no trace of that variable, and I cannot imagine that
uninstalling at-spi2-core would have unset it in all running shells.
> Can you check what im_config sets the QT_IM_MODULE to when ibus is not found?
That
Allan Sandfeld Jensen wrote:
> I am on Debian and found the same thing. Apt-get remove im-config solves the
> issue. Apparently it is a buggy package that forces Qt to use ibus without
> ensuring ibus is launched.
That's not what I saw. Ibus was always launched at login, and im-config seems
to
On Montag, 12. Juni 2017 09:49:43 CEST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > Check your environment. You must have something that tells Qt to use it.
>
> For Qt4 there's QT4_IM_MODULE indeed, and you can configure the input method
> via qtconfig too. For Qt5 I haven't found
Giuseppe D'Angelo wrote:
> https://codereview.qt-project.org/#/c/177188/
Sorry, I was a bit too fast, I'm still at 5.8.0 . Curiously the patch applies
with a bit of fuzz, so apparently wasn't refactored for 5.8?
R.
___
Development mailing list
Thiago Macieira wrote:
> Check your environment. You must have something that tells Qt to use it.
For Qt4 there's QT4_IM_MODULE indeed, and you can configure the input method
via
qtconfig too. For Qt5 I haven't found anything. In the end I did rename ibus-
daemon and ibus-x11, and only then
Il 11/06/2017 10:27, René J. V. Bertin ha scritto:
Out of curiosity I quit iBus.
Coincidence or not, all keyboard input stopped working in all running Qt5 GUI
(KF5) applications after a few keystrokes.
Snooping with xev shows that the X11 events are still being delivered to the
window, and
On Sunday June 11 2017 18:54:03 Allan Sandfeld Jensen wrote:
>So something tells Qt applications to start using ibus when it is launched,
>but they never switch away when it quits.
Couldn't that be simply in
qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
On Sonntag, 11. Juni 2017 10:27:41 CEST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > That's a difference compared to me: I don't have ibus turned on.
>
> Out of curiosity I quit iBus.
>
> Coincidence or not, all keyboard input stopped working in all running Qt5
> GUI (KF5) applications
On Sunday, 11 June 2017 04:12:41 PDT René J. V. Bertin wrote:
> BTW, any suggestions how I can prevent ibus from being started without
> uninstalling it or moving key components out of my path?
Check your environment. You must have something that tells Qt to use it.
--
Thiago Macieira -
BTW, any suggestions how I can prevent ibus from being started without
uninstalling it or moving key components out of my path?
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Thiago Macieira wrote:
> That's a difference compared to me: I don't have ibus turned on.
Out of curiosity I quit iBus.
Coincidence or not, all keyboard input stopped working in all running Qt5 GUI
(KF5) applications after a few keystrokes.
Snooping with xev shows that the X11 events are
17 matches
Mail list logo