Need DBus API to get screen orientation

Bug #1630340 reported by Omer Akram
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Incomplete
Undecided
Unassigned
qtmir (Ubuntu)
Invalid
Undecided
Unassigned
unity8 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

To be effectively implement features like window snapping and dragging of windows in autopilot, we need to know the current height and width of the screen. mirout gives a hard-coded widthXheight, so if we know the orientation we can easily figure out what the real height and width are based on the rotation.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity8 8.14+16.10.20160922-0ubuntu2
Uname: Linux 4.7.0-040700-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue Oct 4 22:53:42 2016
InstallationDate: Installed on 2016-09-21 (12 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Omer Akram (om26er) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Snapping and dragging of windows is part of window management unrelated to dbus.

So is there some context missing here? Is this feature request for test automation or general interactive usage? If the latter then it sounds like the bug title is an inappropriate solution description rather than a problem description.

Changed in canonical-devices-system-image:
status: New → Incomplete
Changed in qtmir (Ubuntu):
status: New → Incomplete
Changed in unity8 (Ubuntu):
status: New → Incomplete
Revision history for this message
Omer Akram (om26er) wrote :

Daniel, yes, it seems I failed to mention that this is needed for autopilot, the tool itself.

description: updated
Changed in canonical-devices-system-image:
status: Incomplete → New
Changed in qtmir (Ubuntu):
status: Incomplete → New
Changed in unity8 (Ubuntu):
status: Incomplete → New
Revision history for this message
Michael Zanetti (mzanetti) wrote :

IMHO this really sounds like you want to start unity8 with with testability enabled so that autopilot can connect to unity8 and get all the things it needs from there...

Exporting those internals additionally on a d-bus interface that would be just used for testing seems a) redundant and b) short-sighted to me. I worry that after this autopilot would need more and more on this interface, while starting it with testability enabled would give you everything at once, just like it is intended for testing.

Changed in unity8 (Ubuntu):
status: New → Incomplete
Changed in qtmir (Ubuntu):
status: New → Invalid
Changed in canonical-devices-system-image:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]

Changed in unity8 (Ubuntu):
status: Incomplete → Expired
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.