Mir

Multi-monitor bug: different resolution

Bug #1200127 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Invalid
Critical
Unassigned

Bug Description

I have a dual screen setup on my desktop via HDMI and VGA connectors (on motherboard) connected via (hdmi and vga) on the screens.

They are full 1080p 22" monitors.

Once booted the two screens are the same. But "resolution" is off, since the trashcan is chopped off on the bottom of the screen. When moving the mouse down, left screen "scrolls" like a surface flinger / vnc to reveal bottom part of the screen, but instead chop off indicators.

The right screen doesn't mirror the "scrolls" / surface flinger.

Tags: multimonitor
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The incorrect resolution causing the trashcan to be chopped off sounds like bug 1102760. However it's only a duplicate of bug 1102760 if the monitors have different resolutions... You seem to describe that they're the same.

The scrolling is something implemented by X. So this might be an XMir issue in how it translates the virtual desktop resolution to Mir.

tags: added: multimonitor
kevin gunn (kgunn72)
Changed in mir:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Alexandros Frantzis (afrantzis)
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

i am able to run/test any proposed patches or builds. Or get any additional debug info / remote access as needed.

kevin gunn (kgunn72)
Changed in xmir:
status: New → Triaged
Changed in xmir:
importance: Undecided → Critical
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Dmittrijs,

A lot has changed in multimonitor since this bug was logged. Can you please try:
    sudo apt-get update
    sudo apt-get dist-upgrade
And let us know how it works for you?

Changed in mir:
status: Triaged → Incomplete
Changed in xmir:
status: Triaged → Incomplete
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Here is a link to video displaying the problem.

This is still an issue with:
libmirclient2 0.0.9+13.10.20130822-0ubuntu1

https://plus.google.com/photos/109160032876474505377/albums/5916113064001064097/5916113066182192562?pid=5916113066182192562&oid=109160032876474505377

I'm using intel drivers, and lightdm fails to come up, unless I comment out type=unity in the snippet unity-system-compositors adds to lightdm.

Changed in xmir:
status: Incomplete → Confirmed
Changed in mir:
status: Incomplete → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Wait a minute; if you have commented out type=unity then you're not using Mir at all. Can you please run:
   ps auxw | grep mir
and
   ps auxw | grep X
and also attach your /var/log/Xorg.0.log

Changed in mir:
status: Confirmed → Incomplete
Changed in xmir:
status: Confirmed → Incomplete
Changed in mir:
assignee: Alexandros Frantzis (afrantzis) → nobody
Revision history for this message
kevin gunn (kgunn72) wrote :

this was incomplete due to not running the correct config.

however, subsequent to that, I believe we now have solutions in place permitting disparate monitor resolutions.
note, there are other specific bugs around resolution changes (e.g. change via system settings) , howeveer those are to be considered seperate

Changed in mir:
status: Incomplete → Fix Committed
Changed in xmir:
status: Incomplete → Fix Committed
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Investigating further I found out I had hybris installed and thus unity-system-compositor was crashing. Upgrading to multi-monitor ppa and uninstalling hybris resolved the issue.

/usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -mir 0 -mirSocket /tmp/mir_socket -nolisten tcp

Does this mean I'm now using Xmir?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

unity-system-compositor is running, and this bug is not present. \o/ all is good.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Yes, that indicates you are using XMir

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

Invalid. Mir was never running in the first place.

Changed in mir:
status: Fix Committed → Invalid
Changed in xmir:
status: Fix Committed → Invalid
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.