From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14206] QT5 touch screen rotation does not work since 2021.05
Date: Fri, 10 Sep 2021 11:55:41 +0000 [thread overview]
Message-ID: <bug-14206-163-AWiXTFb9HI@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14206-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14206
Thomas Ruschival <t.ruschival@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Thomas Ruschival <t.ruschival@gmail.com> ---
It is not a bug but a behavior of Qt5 v5.15.
(https://doc.qt.io/qt-5/inputs-linux-device.html)
The issue can be solved/worked around in two different ways:
Either:
Disable the use of libinput (QT_QPA_EGLFS_NO_LIBINPUT=1) and continue using the
environment variable
QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS=/dev/input/touch:rotate=90
OR:
use the generic platform plugin configuration variable
QT_QPA_GENERIC_PLUGINS=evdevtouch:/dev/input/touch:rotate=90
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-10 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 13:29 [Buildroot] [Bug 14206] New: QT5 touch screen rotation does not work since 2021.05 bugzilla
2021-09-08 12:30 ` [Buildroot] [Bug 14206] " bugzilla
2021-09-10 11:55 ` bugzilla [this message]
2021-09-11 7:59 ` bugzilla
2021-09-11 8:00 ` [Buildroot] [Bug 14206] Kodi: even when not enabled, forcefully selects libevdev and libinput [was: QT5 touch screen rotation does not work since 2021.05] bugzilla
2021-09-17 21:30 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14206-163-AWiXTFb9HI@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.