suspend/gpu_lockup_after_suspend fails

Bug #1172851 reported by Daniel Manrique
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Medium
Sylvain Pineau

Bug Description

This test failed, the error looks legit.

Cannot open display.
Traceback (most recent call last):
  File "/usr/lib/checkbox/bin/gpu_test", line 204, in <module>
    sys.exit(main())
  File "/usr/lib/checkbox/bin/gpu_test", line 162, in main
    shell=True)
  File "/usr/lib/python3.3/subprocess.py", line 586, in check_output
    raise CalledProcessError(retcode, process.args, output=output)
subprocess.CalledProcessError: Command 'wmctrl -l | grep glxgears' returned non-zero exit status 1

This failure happened using plainbox on raring, but it may also happen on checkbox, since we haven't really run SRU testing on raring yet.

Tags: plainbox sru

Related branches

Daniel Manrique (roadmr)
affects: checkbox-satellite → checkbox
Revision history for this message
Daniel Manrique (roadmr) wrote :

I tested this, running the script manually works:

/usr/share/checkbox/scripts/gpu_test

but running through plainbox doesn't:

plainbox run -i suspend/gpu_lockup_after_suspend

plainbox is smart enough to run the dependencies first (suspend_advanced_auto), after suspending and resuming it invokes the lockup test and produces the error seen above.

Note that the job is defined to run as root, this may have something to do with it, however I remember it running OK from within checkbox.

Zygmunt Krynicki (zyga)
Changed in checkbox:
assignee: nobody → Zygmunt Krynicki (zkrynicki)
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

This is _not_ plainbox specific, tested on raring, with plainbox 0.2+bzr2082+bzr10~raring1 and checkbox 0.15.5

zyga@purple:~$ sudo /usr/share/checkbox/scripts/gpu_test
/bin/sh: 1: wmctrl: not found
Traceback (most recent call last):
  File "/usr/share/checkbox/scripts/gpu_test", line 204, in <module>
    sys.exit(main())
  File "/usr/share/checkbox/scripts/gpu_test", line 162, in main
    shell=True)
  File "/usr/lib/python3.3/subprocess.py", line 586, in check_output
    raise CalledProcessError(retcode, process.args, output=output)
subprocess.CalledProcessError: Command 'wmctrl -l | grep glxgears' returned non-zero exit status 1

information type: Proprietary → Public
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

I had a look at this job but it's hard to know what the problem is. The script uses threads, suspends the machine, has barely no comments and uses shell freely.

Changed in checkbox:
assignee: Zygmunt Krynicki (zkrynicki) → nobody
tags: removed: plainbox
Revision history for this message
Sylvain Pineau (sylvain-pineau) wrote :

This script depends on the following packages:

 package.name == 'fwts'
 package.name == 'wmctrl'
 package.name == 'mesa-utils'

without the first two ones, using checkbox from the dev ppa (0.16.1+bzr2092+201304271901~raring1) I have exactly the same error.

So it looks like a missing dependency to me. Please note that these packages are only set as requirements for checkbox-certification.

Revision history for this message
Sylvain Pineau (sylvain-pineau) wrote :

Tested on raring (always with the dev ppa packages) with plainbox.
The trace was incomplete: http://pastebin.ubuntu.com/5615388/

'Cannot open display', it's pkexec fault and only affects plainbox.
pkexec will not allow you to run X11 applications as another user since the $DISPLAY and $XAUTHORITY environment variables are not set.

The only possible fix is to provide a policy file including:
<annotate key="org.freedesktop.policykit.exec.allow_gui">TRUE</annotate>

The checkbox trusted launcher feature will provide such a policy file with support for allow_gui.

Changed in checkbox:
status: New → Triaged
importance: Undecided → Medium
tags: added: plainbox
Changed in checkbox:
assignee: nobody → Sylvain Pineau (sylvain-pineau)
status: Triaged → In Progress
Daniel Manrique (roadmr)
Changed in checkbox:
status: In Progress → Fix Committed
Changed in checkbox:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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