Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-04 Thread Thiago Macieira 
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
> synchronising a few IMAP accounts, that can really get my fans blowing).

That's not D-Bus. That's the progress animation indicating that accounts are 
being checked. Minmise KMail and the problem goes away.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-04 Thread René J . V . Bertin 
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.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-04 Thread René J . V . Bertin 
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
QT_LINUX_ACCESSIBILITY_ALWAYS_ON=0 to force accessibility features OFF.

Lisandro Damián Nicanor Pérez Meyer wrote:

> I have just filled a [debian bug] for this. Allan and everyone: please do
> never hesitate in filing bugs against Debian packages for this or any other

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 synchronising a 
few IMAP accounts, that can really get my fans blowing).

R.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-02 Thread Lisandro Damián Nicanor Pérez Meyer 
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 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 found there's a package called
> im-config where you can configure this. Annoyingly I didn't write down
> exactly where that was on by Ubuntu rig, and judging from the file date it
> was not the
> /etc/defaults/im_config file I thought I remembered it was :-/
>
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.

Btw. In a similar vain of packages having a negative impact on Qt. I also
recomment uninstalling at-spi2-core which sets the environment variable to
force accessibility always on which has a big negative performance impact.


Would it be possible to measure, demonstrate and/or explain the reasons for
this performance impact? It might be of help to convince people to try to
find a better way to only set this variable when needed.

Thanks in advance!
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-02 Thread Lisandro Damián Nicanor Pérez Meyer 
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
> > accessibility interfaces at runtime. On macOS and Windows, the same
> > performance impact is only enabled if you start using a system
> > accessibility feature.
> 
> That's possibly it. A11y team: do you think we can start this only if the
> right hardware is detected?

I have just filled a [debian bug] for this. Allan and everyone: please do 
never hesitate in filing bugs against Debian packages for this or any other 
bug/sugegstion/performance issue you might find. We are mostly 2 people behind 
Qt but really try to give our users the best experience we can.

Pinging me or mitya57 on IRC is also a valid thing to do :-)

Thanks!

[debian bug] 


-- 
http://mx.grulic.org.ar/lurker/message/20081108.174208.4f42e55c.es.html
Así se corrobora el software legal en Argentina

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-09-02 Thread Lisandro Damián Nicanor Pérez Meyer 
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 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 get some length to ensure that applications always use the "best"
> > method available if the user didn't configure things to use a specific
> > method. That's why newly launched Qt applications work fine after exiting
> > ibus. The loss of keyboard input in Qt5 applications is a priori not a
> > packaging fault but a regression in Qt itself.
> > 
> > > Btw. In a similar vain of packages having a negative impact on Qt. I
> > > also
> > > recomment uninstalling at-spi2-core which sets the environment variable
> > > to
> > > force accessibility always on which has a big negative performance
> > > impact.

Right. We where asked to turn it on by default by the a11y team (CCIng). 
Granted we did not know it meant that it will have such a negative impact in 
performance.

> > Thanks for the suggestion, at least I could uninstall that one without
> > taking a sh*load of other packages along with it...
> > What env. variable would that be (I don't want to log off and on AGAIN
> > just
> > yet
> > 
> > :))
> 
> 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
> accessibility interfaces at runtime. On macOS and Windows, the same
> performance impact is only enabled if you start using a system accessibility
> feature.

That's possibly it. A11y team: do you think we can start this only if the 
right hardware is detected?


-- 
Mi experiencia me dice que lo que la gente quiere y necesita -en Indonesia, en
Turquía, en Italia, en los Estados Unidos, en Brasil, en la Argentina o donde
sea- es básicamente lo mismo. La gente quiere comida en la mesa, una vivienda
básica, un gobierno que funcione, que en las fuerzas de seguridad haya
personas confiables, a las que no tengan que tenerles miedo, educación y
salud. ¡La gente de todo el mundo quiere lo mismo!
  Padre Thomas Michel, jesuita, especialista en diálogo interreligioso,
  en una entrevista de Elisabetta Piqué para La Nación, 27/09/2006.
  http://www.lanacion.com.ar/844069

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-12 Thread René J . V . Bertin 
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 variable isn't set at all on my system. That may have to do with the fact 
I'm running Kubuntu 14.04 with self-built Qt5 and KF5 stuff installed into 
/opt/local. But QT4_IM_MODULE=xim, which fits with what I reconfigured as the 
default input method yesterday as well as with what I understand of im-config's 
"auto" setting.

R.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-12 Thread René J . V . Bertin 
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 
get some length to ensure that applications always use the "best" method 
available if the user didn't configure things to use a specific method. That's 
why 
newly launched Qt applications work fine after exiting ibus. The loss of 
keyboard 
input in Qt5 applications is a priori not a packaging fault but a regression in 
Qt itself.

> Btw. In a similar vain of packages having a negative impact on Qt. I also
> recomment uninstalling at-spi2-core which sets the environment variable to
> force accessibility always on which has a big negative performance impact.

Thanks for the suggestion, at least I could uninstall that one without taking a 
sh*load of other packages along with it...
What env. variable would that be (I don't want to log off and on AGAIN just yet 
:))

Cheers,
R.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-12 Thread Allan Sandfeld Jensen 
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 anything. In the end I did rename
> ibus- daemon and ibus-x11, and only then found there's a package called
> im-config where you can configure this. Annoyingly I didn't write down
> exactly where that was on by Ubuntu rig, and judging from the file date it
> was not the
> /etc/defaults/im_config file I thought I remembered it was :-/
> 
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.

Btw. In a similar vain of packages having a negative impact on Qt. I also 
recomment uninstalling at-spi2-core which sets the environment variable to 
force accessibility always on which has a big negative performance impact.

'Allan
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-12 Thread René J . V . Bertin 
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
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-12 Thread René J . V . Bertin 
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 found there's a package called im-config 
where 
you can configure this. Annoyingly I didn't write down exactly where that was 
on 
by Ubuntu rig, and judging from the file date it was not the 
/etc/defaults/im_config file I thought I remembered it was :-/

Giuseppe D'Angelo wrote:

> Does applying
> https://codereview.qt-project.org/#/c/177188/
> help?

The patch applies to 5.9.0 and with it I can follow the described recipe 
without 
losing keyboard input.

R.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-11 Thread Giuseppe D'Angelo 

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 newly launched applications are not affected.

I could try attaching a debugger a next time this happens, where could I set a
breakpoint?


Does applying

https://codereview.qt-project.org/#/c/177188/

help?

Cheers,

--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a KDAB Group company | Tel: UK +44-1625-809908
KDAB - Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-11 Thread René J . V . Bertin 
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 
(qtbase/src/plugins/platforminputcontexts/ibus)?
Sounds like something that might be easier to trace and fix than the 
accent/deadkey issue.

I should add that the recipe I provided to introduce that issue no longer works 
for me now that I figured out how to disable ibus without uninstalling it.

R.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-11 Thread Allan Sandfeld Jensen 
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 after a few keystrokes.
> 
> Snooping with xev shows that the X11 events are still being delivered to the
> window, and newly launched applications are not affected.
> 
> I could try attaching a debugger a next time this happens, where could I set
> a breakpoint?
> 
This is the same behavior I saw. When I had the issue with accents, I started 
ibus, and it fixed it, then I shut down ibus, and the Qt applications that had 
the issue before, and then worked, stopped responding to input, and newly 
launched applications worked but had the issue.

So something tells Qt applications to start using ibus when it is launched, 
but they never switch away when it quits.

`Allan


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-11 Thread Thiago Macieira 
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 - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-11 Thread René J . V . Bertin 
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

Re: [Development] Qt/XCB applications and deadkeys and ibus (which cease working) (and sometimes the entire keyboard in Konsole)

2017-06-11 Thread René J . V . Bertin 
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 still being delivered to the 
window, and newly launched applications are not affected.

I could try attaching a debugger a next time this happens, where could I set a 
breakpoint?

R.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development