Red Hat Bugzilla – Bug 906137
Slide show mode inverts outputs
Last modified: 2013-03-24 18:49:36 EDT
On a T520 laptop, docked and with an external monitor connected via HDMI port on the dock LiberOffice misunderstand what is the internal and what is the external monitor.
If I choose "Display 1" it shows the presentation on the external monitor
If I choose "Display 2 (external)" it shows the presentation on my laptop screen
In the second case it also fails to conceal the gnome-shell bar so the presentation has the bar overlayed
Created attachment 690869 [details]
Does the "right thing" for me with a laptop that's already running, and then I connect to a projector/monitor afterwards. I get the display 1 as the laptop and the "external" display as the right one.
Can I get the output of gcc `pkg-config --cflags --libs gtk+-2.0` screentest.c && ./a.out
monitor 0 is called HDMI3
monitor 1 is called LVDS1
monitor 1 is reported to be the primary. Assuming to be the laptop, typically called LVDS
For "failing to conceal gnome-shell bar" see bug 920697 and its standalone reproducer.
re-reading comment #1, Which monitor is gnome-shell's task-bar on ?
The taskbar is on the laptop monitor.
With a bit of wiggling of xrandr I can get my monitors into the same order as your on one of my laptops and get impress bustage that looks like this.
*grrr*, that's super annoying. gmodule thing returned 0 for the symbol we wanted to use, so into the fallback code, and another bug in that so big chain of stuff turns into "monitor 0 is always the laptop"
libreoffice-22.214.171.124-8.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreoffice-126.96.36.199-8.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libreoffice-188.8.131.52-8.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.