From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15461] New: QtVirtualKeyboard segfaults
Date: Mon, 20 Mar 2023 02:43:26 +0000 [thread overview]
Message-ID: <bug-15461-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15461
Bug ID: 15461
Summary: QtVirtualKeyboard segfaults
Product: buildroot
Version: 2023.02
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: info@resilience-theatre.com
CC: buildroot@uclibc.org
Target Milestone: ---
QtVirtualKeybaord program which works on 2022.02.9 segfaults on 2023.02.
My working defconfig for Pinephone (ARM) fails to run QT/QML program which
incldues virtualkeyboard after upgrade to 2023.02.
Steps to reproduce:
* Clone 2023.02 buildroot
* Arm defconfig with all standard QT packages (5.15.8)
* Setup QT Creator with toolchain and sysroot to BR produced
* Create sample QML application and include QtVirtualKeyboard
* Try to run program
Results on 2023.02:
ASSERT: "targetObjectIndex >= 0" in file
../../include/QtQml/5.15.8/QtQml/private/../../../../../src/qml/qml/qqmlpropertycachecreator_p.h,
line 828
On 2022.02.9 this works without and erros.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-03-20 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 2:43 bugzilla [this message]
2023-03-21 13:23 ` [Buildroot] [Bug 15461] QtVirtualKeyboard segfaults bugzilla
2023-03-21 13:42 ` bugzilla
2023-03-22 0:53 ` bugzilla
2023-03-22 2:08 ` bugzilla
2023-03-22 13:51 ` bugzilla
2023-03-22 16:36 ` bugzilla
2023-06-21 13:08 ` bugzilla
2023-06-21 14:46 ` 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-15461-163@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.