test_hide_osk_when_pickerpanel_opens fails with Qt 5.3.2 on x86

Bug #1382121 reported by Timo Jyrinki
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu UI Toolkit
Fix Released
High
Zsombor Egri
ubuntu-ui-toolkit (Ubuntu)
Fix Released
Undecided
Unassigned
Vivid
Fix Released
Undecided
Unassigned
ubuntu-ui-toolkit (Ubuntu RTM)
In Progress
Critical
Zsombor Egri

Bug Description

See https://launchpadlibrarian.net/187504867/buildlog_ubuntu-utopic-amd64.ubuntu-ui-toolkit_1.1.1279%2B14.10.20141007-0ubuntu2%2Bdisabletest~~1_UPLOADING.txt.gz

---
FAIL! : components::FocusingTests::test_hide_osk_when_pickerpanel_opens() 'OSK is hidden' returned FALSE. ()
   Loc: [/build/buildd/ubuntu-ui-toolkit-1.1.1279+14.10.20141007/tests/unit_x11/tst_components/tst_focus.qml(187)]
---

All Qt 5.3(.2) bugs https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.3

Info about Qt 5.3.2 testing https://wiki.ubuntu.com/Touch/QtTesting

Tags: qt5.3

Related branches

description: updated
tags: added: qt5.3
Revision history for this message
Tim Peeters (tpeeters) wrote :

Can you confirm this locally by running on your pc or device? We get a lot of random failures on jenkins lately.

Changed in ubuntu-ui-toolkit:
status: New → Incomplete
assignee: nobody → Zsombor Egri (zsombi)
importance: Undecided → High
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Confirmed locally.

Changed in ubuntu-ui-toolkit:
status: Incomplete → Confirmed
Revision history for this message
Zsombor Egri (zsombi) wrote :

Tim, Timo: the OSK tests should NOT run on any device, especially not on AMD64, where there's no OSK. Check QT_IM_MODULE env var, as I bet that has a different value than empty string (more precisely it may have 'ibus' set).

As there's no other way to check whether we have OSK or not by checking this env var, having any value but empty string causes these tests to be executed, and will 100% fail if there's no OSK popped up.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

(made the two other bugs duplicate of this)

QT_IM_MODULE is not set, not locally and probably not on builders either. Maybe Qt 5.3.2 itself now sets it during execution or something, if that's the only explanation. In that case checking it's empty wouldn't be a sufficient check on 5.3.2 anymore.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Probably this one, it's never empty:

https://codereview.qt-project.org/#/c/92846/

I guess it would work if every check would check if it's either empty or "compose"?

Revision history for this message
Zsombor Egri (zsombi) wrote :

Aham... how nice!!!!!

Revision history for this message
Zsombor Egri (zsombi) wrote :

One thing I noticed, that since 5.3 we get QT_IM_MODULE set to ibus automatically after installing Qt on Utopic.

Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit:
status: Confirmed → In Progress
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:ubuntu-ui-toolkit/staging at revision None, scheduled for release in ubuntu-ui-toolkit, milestone Unknown

Changed in ubuntu-ui-toolkit:
status: In Progress → Fix Committed
Zoltan Balogh (bzoltan)
Changed in ubuntu-ui-toolkit:
status: Fix Committed → Fix Released
Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit (Ubuntu RTM):
importance: Undecided → Critical
assignee: nobody → Zsombor Egri (zsombi)
status: New → In Progress
Changed in ubuntu-ui-toolkit (Ubuntu):
status: New → Fix Released
Changed in ubuntu-ui-toolkit (Ubuntu Vivid):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.