** Changed in: maliit-framework (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354189
Title:
/usr/lib/arm-linux-
** Branch linked: lp:~michael-sheldon/ubuntu/utopic/maliit-framework
/sync-with-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354189
Title:
/usr/lib/arm-linux-
I searched for qplatforminputcontext and dbus related commits in 5.3.x,
but none seemed to touch the places in code where the trace points to.
But in doing that, I figured out that while QDBus is in qtbase,
MInputContext is not in platforminputcontext (in qtbase) where I
thought it'd be, but
I think this is being caused by the unchecked use of
qGuiApp-focusObject() in minputcontext.cpp:488, it looks like its
possible to cause a crash by typing whilst changing focus, resulting in
maliit attempting to send the event somewhere invalid. There seems to be
a fair amount of unchecked uses of
** Changed in: maliit-framework (Ubuntu)
Assignee: (unassigned) = Michael Sheldon (michael-sheldon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354189
Title:
/usr/lib/arm-linux-
I have another crash here that looks like the same issue .
https://errors.ubuntu.com/bucket/?id=/usr/bin/address-book-
app%3A11%3AQCoreApplication%3A%3AnotifyInternal%3AMInputContext%3A%3AupdatePreeditInternally%3AMInputContext%3A%3AupdatePreedit%3AMInputContext%3A%3Aqt_static_metacall%3AQMetaObject%3A%3Aactivate
also looks like the same issue
** Changed
Unfortunately there are no steps to reproduce, a test that randomly
clicks and swipes on the screen found this crash. I've seen issues in
the systems-settings app not responding to dbus issues after flight mode
is used, I'll try to reproduce this crash manually.
--
You received this bug
https://errors.ubuntu.com/oops/9a0c99f8-1e6d-11e4-b766-fa163e75317b
looks like the same issue, but we didn't get a good stack trace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354189
Title:
** Tags added: qa-daily-testing qasoak rtm14
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New = Confirmed
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Based on the stacktrace qtbase is a more likely place for the problem,
since QDBus is shown.
A reproducable test case would be useful, and with that it would be
great if Qt 5.3.1 could be tested as instructed at
https://wiki.ubuntu.com/Touch/QtTesting. That would tell if there is a
fix available
11 matches
Mail list logo