Am Mittwoch, 9. Dezember 2015 um 00:33:23, schrieb Scott Kostyshak 
<skost...@lyx.org>
> On Wed, Dec 09, 2015 at 06:25:10AM +0100, Kornel Benko wrote:
> > Am Dienstag, 8. Dezember 2015 um 20:09:15, schrieb Scott Kostyshak 
> > <skost...@lyx.org>
> 
> > > > > I will try 5.6 beta when it is released. If I cannot reproduce and you
> > > > > can reproduce, we should confirm we are using the same Qt version and
> > > > > then figure out which difference in our systems causes us to see
> > > > > different behavior.
> > > > 
> > > > That may work. Other possibility is, I can send you a package and you 
> > > > can check if the difference
> > > > is in the compilation, or if our systems have different configuration.
> > > > The package is 27MB big, so better have an ftp server ...
> > > 
> > > That is fine too. I prefer to wait until 5.6.0beta jsut because I plan
> > > on testing that anyway.
> > 
> > I found the reason. I am using xmodmap to configure my keyboard. Somehow 
> > this also changes QT behaviour.
> > Today I disabled the call. Now the menu shortcuts at qt5.5.1 are *working*.
> > This does not please me, because now I don't have my preferred dead keys 
> > etc ..
> > But it explains, why others don't see it.
> > Have to investigate :(
> 
> Good job figuring that out! I would like to learn more about Qt someday
> and even try to be involved with the dev/user mailing list, but that is
> long time away. In this case, it would be nice to create a minimal
> example and ask them what's going on, but I think it would take a lot of
> time.

Looks like 'keycode 133' changed. I had Meta_L, but default now is Super_L. 
Same for 'keycode 134', Meta_R -> Super_R
Works now :), until next change :(

I agree now that #9683 is not a blocker ...

> Scott

        Kornel

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to