Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Key modifier issue with Qt5
Forum Updated to NodeBB v4.3 + New Features

Key modifier issue with Qt5

Scheduled Pinned Locked Moved Unsolved General and Desktop
2 Posts 2 Posters 195 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    kif38
    wrote on last edited by
    #1

    Hi,
    I have a problem for all application relying on Qt5 on my computer: all keyboard input are without modifier: no way to use capital letter or the numerical keyboard for example. Shift, control, ALtGr, caps-lock or num-lock are all without effect.
    The bug can be reproduced with a minimalist application in PyQt5, Pyside2 or in plain C++/Qt5.

    All other application running Qt6, GTK, ... or basic X11 application have no such issue and the keyboard is working as expected.

    More puzzling, the computer has two "seats" under linux, this means there are two GPU, keyboards, mouse, ... and the system is configured to have two users using simultaneously the computer. The bug is occurring only on one of the seat and not on the other. Both are running the XFCE desktop environment.

    I also tried to create a new/fresh user without any configuration file and it sees the same bug.

    I did run the minimalist Qt5 program under "strace" but I did not figure out which library/configuration could be problematic (I could share those files if needed). Is there an equivalent of "xev" to inspect the key-stroke at the Qt5 level ?

    Thanks for your help,

    Jérôme

    Pl45m4P 1 Reply Last reply
    0
    • K kif38

      Hi,
      I have a problem for all application relying on Qt5 on my computer: all keyboard input are without modifier: no way to use capital letter or the numerical keyboard for example. Shift, control, ALtGr, caps-lock or num-lock are all without effect.
      The bug can be reproduced with a minimalist application in PyQt5, Pyside2 or in plain C++/Qt5.

      All other application running Qt6, GTK, ... or basic X11 application have no such issue and the keyboard is working as expected.

      More puzzling, the computer has two "seats" under linux, this means there are two GPU, keyboards, mouse, ... and the system is configured to have two users using simultaneously the computer. The bug is occurring only on one of the seat and not on the other. Both are running the XFCE desktop environment.

      I also tried to create a new/fresh user without any configuration file and it sees the same bug.

      I did run the minimalist Qt5 program under "strace" but I did not figure out which library/configuration could be problematic (I could share those files if needed). Is there an equivalent of "xev" to inspect the key-stroke at the Qt5 level ?

      Thanks for your help,

      Jérôme

      Pl45m4P Offline
      Pl45m4P Offline
      Pl45m4
      wrote on last edited by
      #2

      @kif38 said in Key modifier issue with Qt5:

      The bug can be reproduced with a minimalist application in PyQt5, Pyside2 or in plain C++/Qt5.

      Post one below.

      I assume it's related to your (very special) system and not a general bug in Qt5.
      If this would be a general bug in Qt5 affecting all keyboard modifiers, it would have been fixed long time ago.

      What exact system do you have there?
      What version of Qt5 are you using?


      If debugging is the process of removing software bugs, then programming must be the process of putting them in.

      ~E. W. Dijkstra

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved