Bug 1386948 - LibreOffice Impress displaying slideshow on wrong monitor with Gnome Wayland session (different gdk_screen_get_primary_monitor results on X vs wayland)
Summary: LibreOffice Impress displaying slideshow on wrong monitor with Gnome Wayland ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 25
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 22:42 UTC by Bill
Modified: 2017-12-12 10:53 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:53:14 UTC
Type: Bug


Attachments (Terms of Use)
source of gtk app to list monitors (617 bytes, text/x-csrc)
2016-10-21 15:05 UTC, Caolan McNamara
no flags Details
prebuilt x86_64 demo (8.70 KB, application/x-executable)
2016-10-21 15:06 UTC, Caolan McNamara
no flags Details

Description Bill 2016-10-19 22:42:51 UTC
Description of problem:

On a laptop with an external monitor plugged in. LibreOffice seems to be confused about which monitor is which. It works correctly in the Gnome on X session but gets it the wrong way around and starts the slide show on the latop monitor instead of the external monitor when running on Gnome Wayland session. Clicking the exchange monitor button in Impress doesn't help either.


Version-Release number of selected component (if applicable): libreoffice-impress 5.2.2.2-3.fc25 x86_64


How reproducible: Run Impress slideshow with two monitors on Gnome Wayland session.


Actual results: Impress seems to be confused about which monitor it should be using.

Comment 1 Caolan McNamara 2016-10-20 10:01:48 UTC
I believe we just call gdk_screen_get_primary_monitor and consider the result of that the laptop monitor and the others external monitors. So my immediate assumption is that this gives different results on the same machine in X vs wayland

Comment 2 Caolan McNamara 2016-10-21 15:05:31 UTC
Created attachment 1212872 [details]
source of gtk app to list monitors

build with gcc `pkg-config --cflags --libs gtk+-3.0` demo.c

Comment 3 Caolan McNamara 2016-10-21 15:06:33 UTC
Created attachment 1212873 [details]
prebuilt x86_64 demo

run with chmod a+x ./demo && ./demo

Comment 4 Caolan McNamara 2016-10-21 15:07:44 UTC
Can you run the attachment of comment #3 under X and under wayland and report the values for each case ?

Comment 5 Bill 2016-10-21 22:31:51 UTC
Hi Caolan. I have a problem in that the latest version of mutter (appeared in updates testing yesterday) disables wayland on my hybrid graphics machine. See https://bugzilla.redhat.com/show_bug.cgi?id=1375247. I will only be able to run your test using the old version of mutter. Will do so later today.

Comment 6 Bill 2016-10-21 23:16:33 UTC
I forgot I had an old monitor stored away so I have been able to run the test now.

Results:

Wayland session

Monitor 0 is Philips 190B, default?: yes
Monitor 1 is 0x21ed, default?: no

X11 Session

Monitor 0 is eDP1, default?: yes
Monitor 1 is VGA1, default?: no


The Philips monitor is on an external VGA port. So it does look like the monitors are being reported the wrong way around under Wayland. As I said I can't do this test using the latest mutter. This test is on

 mutter-3.22.1-2.fc25.x86_64

Comment 7 Caolan McNamara 2016-10-22 14:19:27 UTC
Not sure where the fault will lie eventually, but lets move this one layer down then. We use the same gtk gdk_screen_get_primary_monitor call and get different results depending on X vs wayland

Comment 8 Anass Ahmed 2016-10-26 07:08:58 UTC
I confirm that this was happening with me since F24, I used to drag the presentation window to the right monitor, and the timer screen to the other one.

Comment 9 Fedora End Of Life 2017-11-16 19:38:43 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 10 Fedora End Of Life 2017-12-12 10:53:14 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.