Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-18 Thread Peter Wallbridge 
On Sat, Aug 18, 2018 at 9:08 AM Peter Wallbridge 
wrote:

>
>
>
>
> On Sat, Aug 18, 2018 at 9:07 AM Peter Wallbridge 
> wrote:
>
>> Daniel, Here are three more photos. Sent individually because of size
>> limitations.
>>
>> 1.  IMG_2013.JPG   Start of boot up sequence with 3 monitors plugged in.
>>
>> 2. IMG_2014.JPG Continuing boot up sequence.
>>
>> 3. IMG_2015.JPG, Finished booting. Waiting for login. Monitor 2 blank and
>> no input from keyboard or mouse
>>
>>
>> Hope this sheds some more light on the problem.
>>
>> Peter
>>
>> On Fri, Aug 17, 2018 at 8:31 AM Peter Wallbridge 
>> wrote:
>>
>>>
>>> Without 3rd monitor plugged in:
>>>
>>>
>>> peterw@simulator:~$ journalctl -f
>>> -- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
>>> Aug 17 08:26:31 simulator org.blueman.Mechanism[1052]: Unable to init
>>> server: Could not connect: Connection refused
>>> Aug 17 08:26:31 simulator org.blueman.Mechanism[1052]: Unable to init
>>> server: Could not connect: Connection refused
>>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: Starting
>>> blueman-mechanism
>>> Aug 17 08:26:31 simulator dbus-daemon[1052]: [system] Successfully
>>> activated service 'org.blueman.Mechanism'
>>> Aug 17 08:26:31 simulator blueman-mechani[2442]:
>>> gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
>>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading RfKill
>>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Rfcomm
>>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Network
>>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Ppp
>>> Aug 17 08:26:32 simulator gnome-shell[1888]: [AppIndicatorSupport-DEBUG]
>>> Registering StatusNotifierItem :1.56/org/ayatana/NotificationItem/blueman
>>> Aug 17 08:26:43 simulator PackageKit[1635]: search-file transaction
>>> /838_eaaebbdd from uid 1000 finished with success after 33028ms
>>> Aug 17 08:26:44 simulator PackageKit[1635]: search-file transaction
>>> /839_baadeede from uid 1000 finished with success after 506ms
>>> Aug 17 08:26:44 simulator gnome-software[2194]: Failed to find one
>>> package for TheQtCompany-qtcreator-4.7.0-rc1-community.desktop,
>>> /usr/share/applications/TheQtCompany-qtcreator-4.7.0-rc1-community.desktop,
>>> [0]
>>> Aug 17 08:26:44 simulator PackageKit[1635]: search-file transaction
>>> /840_bcebcacd from uid 1000 finished with success after 493ms
>>> Aug 17 08:26:44 simulator gnome-software[2194]: Failed to find one
>>> package for DigiaQt-qtcreator-community.desktop,
>>> /usr/share/applications/DigiaQt-qtcreator-community.desktop, [0]
>>> Aug 17 08:26:45 simulator PackageKit[1635]: search-file transaction
>>> /841_ceaaecae from uid 1000 finished with success after 494ms
>>> Aug 17 08:26:46 simulator PackageKit[1635]: search-file transaction
>>> /842_ceceabce from uid 1000 finished with success after 480ms
>>> Aug 17 08:26:46 simulator gnome-software[2194]: Failed to find one
>>> package for Qt-MaintenanceTool.desktop,
>>> /usr/share/applications/Qt-MaintenanceTool.desktop, [0]
>>> Aug 17 08:26:46 simulator PackageKit[1635]: search-file transaction
>>> /843_aaebdcae from uid 1000 finished with success after 507ms
>>> Aug 17 08:26:47 simulator PackageKit[1635]: search-file transaction
>>> /844_dbcdecaa from uid 1000 finished with success after 491ms
>>> Aug 17 08:26:47 simulator PackageKit[1635]: search-file transaction
>>> /845_daeedeaa from uid 1000 finished with success after 510ms
>>> Aug 17 08:26:48 simulator PackageKit[1635]: search-file transaction
>>> /846_decadede from uid 1000 finished with success after 488ms
>>> Aug 17 08:26:48 simulator PackageKit[1635]: search-file transaction
>>> /847_cecbddbc from uid 1000 finished with success after 491ms
>>> Aug 17 08:26:49 simulator PackageKit[1635]: search-file transaction
>>> /848_edceecce from uid 1000 finished with success after 493ms
>>> Aug 17 08:26:50 simulator PackageKit[1635]: search-file transaction
>>> /849_dbdedeca from uid 1000 finished with success after 509ms
>>> Aug 17 08:26:50 simulator PackageKit[1635]: search-file transaction
>>> /850_eeedaaac from uid 1000 finished with success after 494ms
>>> Aug 17 08:26:51 simulator PackageKit[1635]: search-file transaction
>>> /851_ecaceecc from uid 1000 finished with success after 496ms
>>> Aug 17 08:26:51 simulator PackageKit[1635]: search-file transaction
>>> /852_ddedadbe from uid 1000 finished with success after 519ms
>>> Aug 17 08:26:52 simulator PackageKit[1635]: search-file transaction
>>> /853_abcbbdcd from uid 1000 finished with success after 507ms
>>> Aug 17 08:26:52 simulator PackageKit[1635]: search-file transaction
>>> /854_addbdcea from uid 1000 finished with success after 510ms
>>> Aug 17 08:26:53 simulator PackageKit[1635]: search-file transaction
>>> /855_abdcbedd from uid 1000 finished with success after 493ms
>>> Aug 17 08:26:54 simulator PackageKit[1635]: get-details transaction
>>> /856_edabecee from uid 1000 finished with success after 1148ms
>>> Aug 17 08:26:56

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-18 Thread Peter Wallbridge 
On Sat, Aug 18, 2018 at 9:07 AM Peter Wallbridge 
wrote:

> Daniel, Here are three more photos. Sent individually because of size
> limitations.
>
> 1.  IMG_2013.JPG   Start of boot up sequence with 3 monitors plugged in.
>
> 2. IMG_2014.JPG Continuing boot up sequence.
>
> 3. IMG_2015.JPG, Finished booting. Waiting for login. Monitor 2 blank and
> no input from keyboard or mouse
>
>
> Hope this sheds some more light on the problem.
>
> Peter
>
> On Fri, Aug 17, 2018 at 8:31 AM Peter Wallbridge 
> wrote:
>
>>
>> Without 3rd monitor plugged in:
>>
>>
>> peterw@simulator:~$ journalctl -f
>> -- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
>> Aug 17 08:26:31 simulator org.blueman.Mechanism[1052]: Unable to init
>> server: Could not connect: Connection refused
>> Aug 17 08:26:31 simulator org.blueman.Mechanism[1052]: Unable to init
>> server: Could not connect: Connection refused
>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: Starting
>> blueman-mechanism
>> Aug 17 08:26:31 simulator dbus-daemon[1052]: [system] Successfully
>> activated service 'org.blueman.Mechanism'
>> Aug 17 08:26:31 simulator blueman-mechani[2442]:
>> gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading RfKill
>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Rfcomm
>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Network
>> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Ppp
>> Aug 17 08:26:32 simulator gnome-shell[1888]: [AppIndicatorSupport-DEBUG]
>> Registering StatusNotifierItem :1.56/org/ayatana/NotificationItem/blueman
>> Aug 17 08:26:43 simulator PackageKit[1635]: search-file transaction
>> /838_eaaebbdd from uid 1000 finished with success after 33028ms
>> Aug 17 08:26:44 simulator PackageKit[1635]: search-file transaction
>> /839_baadeede from uid 1000 finished with success after 506ms
>> Aug 17 08:26:44 simulator gnome-software[2194]: Failed to find one
>> package for TheQtCompany-qtcreator-4.7.0-rc1-community.desktop,
>> /usr/share/applications/TheQtCompany-qtcreator-4.7.0-rc1-community.desktop,
>> [0]
>> Aug 17 08:26:44 simulator PackageKit[1635]: search-file transaction
>> /840_bcebcacd from uid 1000 finished with success after 493ms
>> Aug 17 08:26:44 simulator gnome-software[2194]: Failed to find one
>> package for DigiaQt-qtcreator-community.desktop,
>> /usr/share/applications/DigiaQt-qtcreator-community.desktop, [0]
>> Aug 17 08:26:45 simulator PackageKit[1635]: search-file transaction
>> /841_ceaaecae from uid 1000 finished with success after 494ms
>> Aug 17 08:26:46 simulator PackageKit[1635]: search-file transaction
>> /842_ceceabce from uid 1000 finished with success after 480ms
>> Aug 17 08:26:46 simulator gnome-software[2194]: Failed to find one
>> package for Qt-MaintenanceTool.desktop,
>> /usr/share/applications/Qt-MaintenanceTool.desktop, [0]
>> Aug 17 08:26:46 simulator PackageKit[1635]: search-file transaction
>> /843_aaebdcae from uid 1000 finished with success after 507ms
>> Aug 17 08:26:47 simulator PackageKit[1635]: search-file transaction
>> /844_dbcdecaa from uid 1000 finished with success after 491ms
>> Aug 17 08:26:47 simulator PackageKit[1635]: search-file transaction
>> /845_daeedeaa from uid 1000 finished with success after 510ms
>> Aug 17 08:26:48 simulator PackageKit[1635]: search-file transaction
>> /846_decadede from uid 1000 finished with success after 488ms
>> Aug 17 08:26:48 simulator PackageKit[1635]: search-file transaction
>> /847_cecbddbc from uid 1000 finished with success after 491ms
>> Aug 17 08:26:49 simulator PackageKit[1635]: search-file transaction
>> /848_edceecce from uid 1000 finished with success after 493ms
>> Aug 17 08:26:50 simulator PackageKit[1635]: search-file transaction
>> /849_dbdedeca from uid 1000 finished with success after 509ms
>> Aug 17 08:26:50 simulator PackageKit[1635]: search-file transaction
>> /850_eeedaaac from uid 1000 finished with success after 494ms
>> Aug 17 08:26:51 simulator PackageKit[1635]: search-file transaction
>> /851_ecaceecc from uid 1000 finished with success after 496ms
>> Aug 17 08:26:51 simulator PackageKit[1635]: search-file transaction
>> /852_ddedadbe from uid 1000 finished with success after 519ms
>> Aug 17 08:26:52 simulator PackageKit[1635]: search-file transaction
>> /853_abcbbdcd from uid 1000 finished with success after 507ms
>> Aug 17 08:26:52 simulator PackageKit[1635]: search-file transaction
>> /854_addbdcea from uid 1000 finished with success after 510ms
>> Aug 17 08:26:53 simulator PackageKit[1635]: search-file transaction
>> /855_abdcbedd from uid 1000 finished with success after 493ms
>> Aug 17 08:26:54 simulator PackageKit[1635]: get-details transaction
>> /856_edabecee from uid 1000 finished with success after 1148ms
>> Aug 17 08:26:56 simulator dbus-daemon[1052]: [system] Failed to activate
>> service 'org.bluez': timed out (service_start_timeout=25000ms)
>> Aug 17 08:26:56 simulator

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-18 Thread Peter Wallbridge 
Daniel, Here are three more photos. Sent individually because of size
limitations.

1.  IMG_2013.JPG   Start of boot up sequence with 3 monitors plugged in.

2. IMG_2014.JPG Continuing boot up sequence.

3. IMG_2015.JPG, Finished booting. Waiting for login. Monitor 2 blank and
no input from keyboard or mouse


Hope this sheds some more light on the problem.

Peter

On Fri, Aug 17, 2018 at 8:31 AM Peter Wallbridge 
wrote:

>
> Without 3rd monitor plugged in:
>
>
> peterw@simulator:~$ journalctl -f
> -- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
> Aug 17 08:26:31 simulator org.blueman.Mechanism[1052]: Unable to init
> server: Could not connect: Connection refused
> Aug 17 08:26:31 simulator org.blueman.Mechanism[1052]: Unable to init
> server: Could not connect: Connection refused
> Aug 17 08:26:31 simulator blueman-mechanism[2442]: Starting
> blueman-mechanism
> Aug 17 08:26:31 simulator dbus-daemon[1052]: [system] Successfully
> activated service 'org.blueman.Mechanism'
> Aug 17 08:26:31 simulator blueman-mechani[2442]:
> gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading RfKill
> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Rfcomm
> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Network
> Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Ppp
> Aug 17 08:26:32 simulator gnome-shell[1888]: [AppIndicatorSupport-DEBUG]
> Registering StatusNotifierItem :1.56/org/ayatana/NotificationItem/blueman
> Aug 17 08:26:43 simulator PackageKit[1635]: search-file transaction
> /838_eaaebbdd from uid 1000 finished with success after 33028ms
> Aug 17 08:26:44 simulator PackageKit[1635]: search-file transaction
> /839_baadeede from uid 1000 finished with success after 506ms
> Aug 17 08:26:44 simulator gnome-software[2194]: Failed to find one package
> for TheQtCompany-qtcreator-4.7.0-rc1-community.desktop,
> /usr/share/applications/TheQtCompany-qtcreator-4.7.0-rc1-community.desktop,
> [0]
> Aug 17 08:26:44 simulator PackageKit[1635]: search-file transaction
> /840_bcebcacd from uid 1000 finished with success after 493ms
> Aug 17 08:26:44 simulator gnome-software[2194]: Failed to find one package
> for DigiaQt-qtcreator-community.desktop,
> /usr/share/applications/DigiaQt-qtcreator-community.desktop, [0]
> Aug 17 08:26:45 simulator PackageKit[1635]: search-file transaction
> /841_ceaaecae from uid 1000 finished with success after 494ms
> Aug 17 08:26:46 simulator PackageKit[1635]: search-file transaction
> /842_ceceabce from uid 1000 finished with success after 480ms
> Aug 17 08:26:46 simulator gnome-software[2194]: Failed to find one package
> for Qt-MaintenanceTool.desktop,
> /usr/share/applications/Qt-MaintenanceTool.desktop, [0]
> Aug 17 08:26:46 simulator PackageKit[1635]: search-file transaction
> /843_aaebdcae from uid 1000 finished with success after 507ms
> Aug 17 08:26:47 simulator PackageKit[1635]: search-file transaction
> /844_dbcdecaa from uid 1000 finished with success after 491ms
> Aug 17 08:26:47 simulator PackageKit[1635]: search-file transaction
> /845_daeedeaa from uid 1000 finished with success after 510ms
> Aug 17 08:26:48 simulator PackageKit[1635]: search-file transaction
> /846_decadede from uid 1000 finished with success after 488ms
> Aug 17 08:26:48 simulator PackageKit[1635]: search-file transaction
> /847_cecbddbc from uid 1000 finished with success after 491ms
> Aug 17 08:26:49 simulator PackageKit[1635]: search-file transaction
> /848_edceecce from uid 1000 finished with success after 493ms
> Aug 17 08:26:50 simulator PackageKit[1635]: search-file transaction
> /849_dbdedeca from uid 1000 finished with success after 509ms
> Aug 17 08:26:50 simulator PackageKit[1635]: search-file transaction
> /850_eeedaaac from uid 1000 finished with success after 494ms
> Aug 17 08:26:51 simulator PackageKit[1635]: search-file transaction
> /851_ecaceecc from uid 1000 finished with success after 496ms
> Aug 17 08:26:51 simulator PackageKit[1635]: search-file transaction
> /852_ddedadbe from uid 1000 finished with success after 519ms
> Aug 17 08:26:52 simulator PackageKit[1635]: search-file transaction
> /853_abcbbdcd from uid 1000 finished with success after 507ms
> Aug 17 08:26:52 simulator PackageKit[1635]: search-file transaction
> /854_addbdcea from uid 1000 finished with success after 510ms
> Aug 17 08:26:53 simulator PackageKit[1635]: search-file transaction
> /855_abdcbedd from uid 1000 finished with success after 493ms
> Aug 17 08:26:54 simulator PackageKit[1635]: get-details transaction
> /856_edabecee from uid 1000 finished with success after 1148ms
> Aug 17 08:26:56 simulator dbus-daemon[1052]: [system] Failed to activate
> service 'org.bluez': timed out (service_start_timeout=25000ms)
> Aug 17 08:26:56 simulator blueman.desktop[2200]:
> /usr/lib/python3/dist-packages/blueman/plugins/applet/AppIndicator.py:8:
> PyGIWarning: AppIndicator3 was imported without specifying a version

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-17 Thread Peter Wallbridge 
Without 3rd monitor plugged in:


peterw@simulator:~$ journalctl -f
-- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
Aug 17 08:26:31 simulator org.blueman.Mechanism[1052]: Unable to init
server: Could not connect: Connection refused
Aug 17 08:26:31 simulator org.blueman.Mechanism[1052]: Unable to init
server: Could not connect: Connection refused
Aug 17 08:26:31 simulator blueman-mechanism[2442]: Starting
blueman-mechanism
Aug 17 08:26:31 simulator dbus-daemon[1052]: [system] Successfully
activated service 'org.blueman.Mechanism'
Aug 17 08:26:31 simulator blueman-mechani[2442]:
gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading RfKill
Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Rfcomm
Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Network
Aug 17 08:26:31 simulator blueman-mechanism[2442]: loading Ppp
Aug 17 08:26:32 simulator gnome-shell[1888]: [AppIndicatorSupport-DEBUG]
Registering StatusNotifierItem :1.56/org/ayatana/NotificationItem/blueman
Aug 17 08:26:43 simulator PackageKit[1635]: search-file transaction
/838_eaaebbdd from uid 1000 finished with success after 33028ms
Aug 17 08:26:44 simulator PackageKit[1635]: search-file transaction
/839_baadeede from uid 1000 finished with success after 506ms
Aug 17 08:26:44 simulator gnome-software[2194]: Failed to find one package
for TheQtCompany-qtcreator-4.7.0-rc1-community.desktop,
/usr/share/applications/TheQtCompany-qtcreator-4.7.0-rc1-community.desktop,
[0]
Aug 17 08:26:44 simulator PackageKit[1635]: search-file transaction
/840_bcebcacd from uid 1000 finished with success after 493ms
Aug 17 08:26:44 simulator gnome-software[2194]: Failed to find one package
for DigiaQt-qtcreator-community.desktop,
/usr/share/applications/DigiaQt-qtcreator-community.desktop, [0]
Aug 17 08:26:45 simulator PackageKit[1635]: search-file transaction
/841_ceaaecae from uid 1000 finished with success after 494ms
Aug 17 08:26:46 simulator PackageKit[1635]: search-file transaction
/842_ceceabce from uid 1000 finished with success after 480ms
Aug 17 08:26:46 simulator gnome-software[2194]: Failed to find one package
for Qt-MaintenanceTool.desktop,
/usr/share/applications/Qt-MaintenanceTool.desktop, [0]
Aug 17 08:26:46 simulator PackageKit[1635]: search-file transaction
/843_aaebdcae from uid 1000 finished with success after 507ms
Aug 17 08:26:47 simulator PackageKit[1635]: search-file transaction
/844_dbcdecaa from uid 1000 finished with success after 491ms
Aug 17 08:26:47 simulator PackageKit[1635]: search-file transaction
/845_daeedeaa from uid 1000 finished with success after 510ms
Aug 17 08:26:48 simulator PackageKit[1635]: search-file transaction
/846_decadede from uid 1000 finished with success after 488ms
Aug 17 08:26:48 simulator PackageKit[1635]: search-file transaction
/847_cecbddbc from uid 1000 finished with success after 491ms
Aug 17 08:26:49 simulator PackageKit[1635]: search-file transaction
/848_edceecce from uid 1000 finished with success after 493ms
Aug 17 08:26:50 simulator PackageKit[1635]: search-file transaction
/849_dbdedeca from uid 1000 finished with success after 509ms
Aug 17 08:26:50 simulator PackageKit[1635]: search-file transaction
/850_eeedaaac from uid 1000 finished with success after 494ms
Aug 17 08:26:51 simulator PackageKit[1635]: search-file transaction
/851_ecaceecc from uid 1000 finished with success after 496ms
Aug 17 08:26:51 simulator PackageKit[1635]: search-file transaction
/852_ddedadbe from uid 1000 finished with success after 519ms
Aug 17 08:26:52 simulator PackageKit[1635]: search-file transaction
/853_abcbbdcd from uid 1000 finished with success after 507ms
Aug 17 08:26:52 simulator PackageKit[1635]: search-file transaction
/854_addbdcea from uid 1000 finished with success after 510ms
Aug 17 08:26:53 simulator PackageKit[1635]: search-file transaction
/855_abdcbedd from uid 1000 finished with success after 493ms
Aug 17 08:26:54 simulator PackageKit[1635]: get-details transaction
/856_edabecee from uid 1000 finished with success after 1148ms
Aug 17 08:26:56 simulator dbus-daemon[1052]: [system] Failed to activate
service 'org.bluez': timed out (service_start_timeout=25000ms)
Aug 17 08:26:56 simulator blueman.desktop[2200]:
/usr/lib/python3/dist-packages/blueman/plugins/applet/AppIndicator.py:8:
PyGIWarning: AppIndicator3 was imported without specifying a version first.
Use gi.require_version('AppIndicator3', '0.1') before import to ensure that
the right version gets loaded.
Aug 17 08:26:56 simulator blueman.desktop[2200]:   from gi.repository
import AppIndicator3 as girAppIndicator
Aug 17 08:26:56 simulator blueman.desktop[2200]: Traceback (most recent
call last):
Aug 17 08:26:56 simulator blueman.desktop[2200]:   File
"/usr/lib/python3/dist-packages/blueman/plugins/BasePlugin.py", line 54, in
_load
Aug 17 08:26:56 simulator blueman.desktop[2200]: self.on_load(parent)
Aug 17 08:26:56 simulator blueman.desktop[2200]:   File

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-16 Thread Peter Wallbridge 
The bug shows up now even in xfce4. It did not earlier with 17.04. Now all
the managers show up the bug.

Will do the other tests later. It is now 1.30 am and I have to get some
sleep.

Thanks

Peter


On Fri, Aug 17, 2018 at 1:00 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> That log appears to be from XFCE which you said does not exhibit the
> bug.
>
> Please do the 3-monitors test with gnome-shell, and run 'journalctl -f'
> there.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Incomplete
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-ati package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:
> core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-16 Thread Peter Wallbridge 
When I use ubuntu on wayland, the third screen is displayed, but the second
screen is not and there is no keyboard or mouse  input. Have to reboot with
the screen unplugged.

Peter

On Fri, Aug 17, 2018 at 12:29 AM Peter Wallbridge 
wrote:

> Nothing normally
> The following with the third monitor plugged in:
> peterw@simulator:~$ journalctl -f
> -- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769
> 772 800 +hsync +vsync (60.0 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771
> 777 806 -hsync -vsync (48.4 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604
> 625 +hsync +vsync (46.9 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865
> 868 900 +hsync +vsync (67.5 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025
> 1028 1066 +hsync +vsync (64.0 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080
> 1081 1084 1118 -hsync +vsync (67.1 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (EE)
> RADEON(0): failed to set mode: Invalid argument
> Aug 17 00:26:53 simulator xfsettingsd[1902]: Failed to configure CRTC 118.
> Aug 17 00:26:53 simulator kernel: [drm:atombios_crtc_mode_fixup [radeon]]
> *ERROR* unable to allocate a PPLL
> Aug 17 00:26:53 simulator kernel: [drm:drm_crtc_helper_set_config
> [drm_kms_helper]] *ERROR* failed to set mode on [CRTC:41:crtc-1]
> Aug 17 00:28:10 simulator xfce4-terminal[28461]:
> gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed
>
>
>
> On Thu, Aug 16, 2018 at 10:05 PM Daniel van Vugt <
> daniel.van.v...@canonical.com> wrote:
>
>> Going back to your JournalErrors.txt:
>>
>> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
>> RADEON(0): Page flip failed: Invalid argument
>> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
>> RADEON(0): present flip failed
>> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
>> RADEON(0): flip queue failed: Invalid argument
>>
>> I would like to verify if those errors correlate with the problem. Can
>> you please run:
>>
>>   journalctl -f
>>
>> and see if those errors only occur when trying to drive 3 monitors?
>>
>> Do the errors go away when only 2 monitors are plugged in?
>>
>> ** Also affects: xserver-xorg-video-ati (Ubuntu)
>>Importance: Undecided
>>Status: New
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1725836
>>
>> Title:
>>   No more than 2 displays work simultaneously
>>
>> Status in Mutter:
>>   Incomplete
>> Status in gnome-shell package in Ubuntu:
>>   Incomplete
>> Status in mutter package in Ubuntu:
>>   Incomplete
>> Status in xorg-server package in Ubuntu:
>>   Incomplete
>> Status in xserver-xorg-video-ati package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   I have three displays that worked fine in 17.04.
>>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>>   All three seem to be properly specified in monitors.xml.
>>   The display setup scree detects all three.
>>   UBUNTU 17.10
>>   AMD PitcairnLSB Version:
>> core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
>>   ---
>>   ApportVersion: 2.20.7-0ubuntu3
>>   Architecture: amd64
>>   CurrentDesktop: ubuntu:GNOME
>>   DisplayManager: gdm3
>>   DistroRelease: Ubuntu 17.10
>>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
>> (20161012.2)
>>   Package: mutter
>>   PackageArchitecture: amd64
>>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>>   Tags:  artful
>>   Uname: Linux 4.13.0-16-generic x86_64
>>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>>   _MarkForUpload: True
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>>
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-16 Thread Peter Wallbridge 
Nothing normally
The following with the third monitor plugged in:
peterw@simulator:~$ journalctl -f
-- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769
772 800 +hsync +vsync (60.0 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771
777 806 -hsync -vsync (48.4 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604
625 +hsync +vsync (46.9 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865
868 900 +hsync +vsync (67.5 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025
1028 1066 +hsync +vsync (64.0 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080
1081 1084 1118 -hsync +vsync (67.1 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (EE)
RADEON(0): failed to set mode: Invalid argument
Aug 17 00:26:53 simulator xfsettingsd[1902]: Failed to configure CRTC 118.
Aug 17 00:26:53 simulator kernel: [drm:atombios_crtc_mode_fixup [radeon]]
*ERROR* unable to allocate a PPLL
Aug 17 00:26:53 simulator kernel: [drm:drm_crtc_helper_set_config
[drm_kms_helper]] *ERROR* failed to set mode on [CRTC:41:crtc-1]
Aug 17 00:28:10 simulator xfce4-terminal[28461]:
gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed


On Thu, Aug 16, 2018 at 10:05 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Going back to your JournalErrors.txt:
>
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): Page flip failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
> RADEON(0): present flip failed
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): flip queue failed: Invalid argument
>
> I would like to verify if those errors correlate with the problem. Can
> you please run:
>
>   journalctl -f
>
> and see if those errors only occur when trying to drive 3 monitors?
>
> Do the errors go away when only 2 monitors are plugged in?
>
> ** Also affects: xserver-xorg-video-ati (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Incomplete
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-ati package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:
> core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-16 Thread Peter Wallbridge 
Here are three photos that might help.


I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
keyboard will not be active


1  - img_2008.jpg Showing all three terminals plugged in


2. img 2010 showing display screen (All displays appear to be available.


3. img-2011.jpg


As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears


Hope this is of some help


I will have to send the photos seperately


On Thu, Aug 16, 2018 at 11:20 AM Peter Wallbridge 
wrote:

> Here are three photos that might help.
>
>
> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
> keyboard will not be active
>
>
> 1  - img_2008.jpg Showing all three terminals plugged in
>
>
> 2. img 2010 showing display screen (All displays appear to be available.
>
>
> 3. img-2011.jpg
>
>
> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>
>
> Hope this is of some help
>
> Peter
>
>
>
> On Thu, Aug 16, 2018 at 7:07 AM Peter Wallbridge 
> wrote:
>
>> 1... Output of xrandr and lspci
>>
>>  xrandr
>> Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
>> DisplayPort-0 disconnected (normal left inverted right x axis y axis)
>> HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
>> axis) 477mm x 268mm
>>1920x1080 60.00*+  60.0050.0059.94
>>1920x1080i60.0050.0059.94
>>1680x1050 59.88
>>1600x900  60.00
>>1280x1024 75.0260.02
>>1280x960  60.00
>>1280x800  59.91
>>1152x864  75.00
>>1280x720  60.0050.0059.94
>>1024x768  75.0360.00
>>1024x576  59.97
>>832x624   74.55
>>800x600   75.0060.32
>>720x576   50.00
>>720x576i  50.00
>>720x480   60.0059.94
>>720x480i  60.0059.94
>>640x480   75.0060.0059.94
>>720x400   70.08
>> DVI-0 disconnected (normal left inverted right x axis y axis)
>> DVI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis
>> y axis) 477mm x 268mm
>>1920x1080 60.00*+
>>1280x1024 75.0260.02
>>1152x864  75.00
>>1024x768  75.0360.00
>>800x600   75.0060.32
>>640x480   75.0059.94
>>720x400   70.08
>> VGA-1-1 disconnected (normal left inverted right x axis y axis)
>> HDMI-1-1 disconnected (normal left inverted right x axis y axis)
>> HDMI-1-2 disconnected (normal left inverted right x axis y axis)
>>
>>
>> 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
>> Controller (rev 06)
>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>> Controller
>> Kernel driver in use: hsw_uncore
>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>> Processor PCI Express x16 Controller (rev 06)
>> Kernel driver in use: pcieport
>> Kernel modules: shpchp
>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>> Gen Core Processor Integrated Graphics Controller (rev 06)
>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>> Processor Integrated Graphics Controller
>> Kernel driver in use: i915
>> Kernel modules: i915
>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>> Processor HD Audio Controller (rev 06)
>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>> Audio Controller
>> Kernel driver in use: snd_hda_intel
>> Kernel modules: snd_hda_intel
>> 00:14.0 USB controller: I00:00.0 Host bridge: Intel Corporation 4th Gen
>> Core Processor DRAM Controller (rev 06)
>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>> Controller
>> Kernel driver in use: hsw_uncore
>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>> Processor PCI Express x16 Controller (rev 06)
>> Kernel driver in use: pcieport
>> Kernel modules: shpchp
>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>> Gen Core Processor Integrated Graphics Controller (rev 06)
>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>> Processor Integrated Graphics Controller
>> Kernel driver in use: i915
>> Kernel modules: i915
>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>> Processor HD Audio Controller (rev 06)
>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>> Audio Controller
>> Kernel driver in use: snd_hda_intel
>> Kernel modules: snd_hda_intel
>> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>> Family USB xHCI (rev 05)
>> Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset
>> Family USB xHCI
>> Kernel driver in use: xhci_hcd
>> 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
>> Chipset Family MEI Controller #1 (rev 04)
>> Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset
>> Family MEI Controller
>> Kernel driver in use: mei_me
>> Kernel modules:

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-16 Thread Peter Wallbridge 
On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge 
wrote:

> Here are three photos that might help.
>
>
> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
> keyboard will not be active
>
>
> 1  - img_2008.jpg Showing all three terminals plugged in
>
>
> 2. img 2010 showing display screen (All displays appear to be available.
>
>
> 3. img-2011.jpg
>
>
> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>
>
> Hope this is of some help
>
>
> I will have to send the photos seperately
>
>
> On Thu, Aug 16, 2018 at 11:20 AM Peter Wallbridge 
> wrote:
>
>> Here are three photos that might help.
>>
>>
>> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
>> keyboard will not be active
>>
>>
>> 1  - img_2008.jpg Showing all three terminals plugged in
>>
>>
>> 2. img 2010 showing display screen (All displays appear to be available.
>>
>>
>> 3. img-2011.jpg
>>
>>
>> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>>
>>
>> Hope this is of some help
>>
>> Peter
>>
>>
>>
>> On Thu, Aug 16, 2018 at 7:07 AM Peter Wallbridge 
>> wrote:
>>
>>> 1... Output of xrandr and lspci
>>>
>>>  xrandr
>>> Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
>>> DisplayPort-0 disconnected (normal left inverted right x axis y axis)
>>> HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
>>> axis) 477mm x 268mm
>>>1920x1080 60.00*+  60.0050.0059.94
>>>1920x1080i60.0050.0059.94
>>>1680x1050 59.88
>>>1600x900  60.00
>>>1280x1024 75.0260.02
>>>1280x960  60.00
>>>1280x800  59.91
>>>1152x864  75.00
>>>1280x720  60.0050.0059.94
>>>1024x768  75.0360.00
>>>1024x576  59.97
>>>832x624   74.55
>>>800x600   75.0060.32
>>>720x576   50.00
>>>720x576i  50.00
>>>720x480   60.0059.94
>>>720x480i  60.0059.94
>>>640x480   75.0060.0059.94
>>>720x400   70.08
>>> DVI-0 disconnected (normal left inverted right x axis y axis)
>>> DVI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis
>>> y axis) 477mm x 268mm
>>>1920x1080 60.00*+
>>>1280x1024 75.0260.02
>>>1152x864  75.00
>>>1024x768  75.0360.00
>>>800x600   75.0060.32
>>>640x480   75.0059.94
>>>720x400   70.08
>>> VGA-1-1 disconnected (normal left inverted right x axis y axis)
>>> HDMI-1-1 disconnected (normal left inverted right x axis y axis)
>>> HDMI-1-2 disconnected (normal left inverted right x axis y axis)
>>>
>>>
>>> 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
>>> Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>>> Controller
>>> Kernel driver in use: hsw_uncore
>>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor PCI Express x16 Controller (rev 06)
>>> Kernel driver in use: pcieport
>>> Kernel modules: shpchp
>>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>>> Gen Core Processor Integrated Graphics Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>>> Processor Integrated Graphics Controller
>>> Kernel driver in use: i915
>>> Kernel modules: i915
>>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor HD Audio Controller (rev 06)
>>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>>> Audio Controller
>>> Kernel driver in use: snd_hda_intel
>>> Kernel modules: snd_hda_intel
>>> 00:14.0 USB controller: I00:00.0 Host bridge: Intel Corporation 4th Gen
>>> Core Processor DRAM Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>>> Controller
>>> Kernel driver in use: hsw_uncore
>>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor PCI Express x16 Controller (rev 06)
>>> Kernel driver in use: pcieport
>>> Kernel modules: shpchp
>>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>>> Gen Core Processor Integrated Graphics Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>>> Processor Integrated Graphics Controller
>>> Kernel driver in use: i915
>>> Kernel modules: i915
>>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor HD Audio Controller (rev 06)
>>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>>> Audio Controller
>>> Kernel driver in use: snd_hda_intel
>>> Kernel modules: snd_hda_intel
>>> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>>> Family USB xHCI (rev 05)
>>> Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset
>>> Family USB xHCI
>>> Kernel driver in use: xhci_hcd
>>> 00:16.0 Communication controller: Intel Corporation 8

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-16 Thread Peter Wallbridge 
On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge 
wrote:

> Here are three photos that might help.
>
>
> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
> keyboard will not be active
>
>
> 1  - img_2008.jpg Showing all three terminals plugged in
>
>
> 2. img 2010 showing display screen (All displays appear to be available.
>
>
> 3. img-2011.jpg
>
>
> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>
>
> Hope this is of some help
>
>
> I will have to send the photos seperately
>
>
> On Thu, Aug 16, 2018 at 11:20 AM Peter Wallbridge 
> wrote:
>
>> Here are three photos that might help.
>>
>>
>> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
>> keyboard will not be active
>>
>>
>> 1  - img_2008.jpg Showing all three terminals plugged in
>>
>>
>> 2. img 2010 showing display screen (All displays appear to be available.
>>
>>
>> 3. img-2011.jpg
>>
>>
>> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>>
>>
>> Hope this is of some help
>>
>> Peter
>>
>>
>>
>> On Thu, Aug 16, 2018 at 7:07 AM Peter Wallbridge 
>> wrote:
>>
>>> 1... Output of xrandr and lspci
>>>
>>>  xrandr
>>> Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
>>> DisplayPort-0 disconnected (normal left inverted right x axis y axis)
>>> HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
>>> axis) 477mm x 268mm
>>>1920x1080 60.00*+  60.0050.0059.94
>>>1920x1080i60.0050.0059.94
>>>1680x1050 59.88
>>>1600x900  60.00
>>>1280x1024 75.0260.02
>>>1280x960  60.00
>>>1280x800  59.91
>>>1152x864  75.00
>>>1280x720  60.0050.0059.94
>>>1024x768  75.0360.00
>>>1024x576  59.97
>>>832x624   74.55
>>>800x600   75.0060.32
>>>720x576   50.00
>>>720x576i  50.00
>>>720x480   60.0059.94
>>>720x480i  60.0059.94
>>>640x480   75.0060.0059.94
>>>720x400   70.08
>>> DVI-0 disconnected (normal left inverted right x axis y axis)
>>> DVI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis
>>> y axis) 477mm x 268mm
>>>1920x1080 60.00*+
>>>1280x1024 75.0260.02
>>>1152x864  75.00
>>>1024x768  75.0360.00
>>>800x600   75.0060.32
>>>640x480   75.0059.94
>>>720x400   70.08
>>> VGA-1-1 disconnected (normal left inverted right x axis y axis)
>>> HDMI-1-1 disconnected (normal left inverted right x axis y axis)
>>> HDMI-1-2 disconnected (normal left inverted right x axis y axis)
>>>
>>>
>>> 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
>>> Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>>> Controller
>>> Kernel driver in use: hsw_uncore
>>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor PCI Express x16 Controller (rev 06)
>>> Kernel driver in use: pcieport
>>> Kernel modules: shpchp
>>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>>> Gen Core Processor Integrated Graphics Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>>> Processor Integrated Graphics Controller
>>> Kernel driver in use: i915
>>> Kernel modules: i915
>>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor HD Audio Controller (rev 06)
>>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>>> Audio Controller
>>> Kernel driver in use: snd_hda_intel
>>> Kernel modules: snd_hda_intel
>>> 00:14.0 USB controller: I00:00.0 Host bridge: Intel Corporation 4th Gen
>>> Core Processor DRAM Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>>> Controller
>>> Kernel driver in use: hsw_uncore
>>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor PCI Express x16 Controller (rev 06)
>>> Kernel driver in use: pcieport
>>> Kernel modules: shpchp
>>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>>> Gen Core Processor Integrated Graphics Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>>> Processor Integrated Graphics Controller
>>> Kernel driver in use: i915
>>> Kernel modules: i915
>>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor HD Audio Controller (rev 06)
>>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>>> Audio Controller
>>> Kernel driver in use: snd_hda_intel
>>> Kernel modules: snd_hda_intel
>>> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>>> Family USB xHCI (rev 05)
>>> Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset
>>> Family USB xHCI
>>> Kernel driver in use: xhci_hcd
>>> 00:16.0 Communication controller: Intel Corporation 8

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-16 Thread Peter Wallbridge 
1... Output of xrandr and lspci

 xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
axis) 477mm x 268mm
   1920x1080 60.00*+  60.0050.0059.94
   1920x1080i60.0050.0059.94
   1680x1050 59.88
   1600x900  60.00
   1280x1024 75.0260.02
   1280x960  60.00
   1280x800  59.91
   1152x864  75.00
   1280x720  60.0050.0059.94
   1024x768  75.0360.00
   1024x576  59.97
   832x624   74.55
   800x600   75.0060.32
   720x576   50.00
   720x576i  50.00
   720x480   60.0059.94
   720x480i  60.0059.94
   640x480   75.0060.0059.94
   720x400   70.08
DVI-0 disconnected (normal left inverted right x axis y axis)
DVI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 477mm x 268mm
   1920x1080 60.00*+
   1280x1024 75.0260.02
   1152x864  75.00
   1024x768  75.0360.00
   800x600   75.0060.32
   640x480   75.0059.94
   720x400   70.08
VGA-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)


00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
Controller
Kernel driver in use: hsw_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor PCI Express x16 Controller (rev 06)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
Processor Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller (rev 06)
Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller: I00:00.0 Host bridge: Intel Corporation 4th Gen
Core Processor DRAM Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
Controller
Kernel driver in use: hsw_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor PCI Express x16 Controller (rev 06)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
Processor Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller (rev 06)
Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB xHCI (rev 05)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family
USB xHCI
Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V
(rev 05)
Subsystem: Gigabyte Technology Co., Ltd Ethernet Connection I217-V
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #2 (rev 05)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family
USB EHCI
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset High
Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family
PCI Express Root Port #1 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family
PCI Express Root Port #4 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #1 (rev 05)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family
USB EHCI
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation B85

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2018-08-15 Thread Peter Wallbridge 
I am using 18.04 and bug still exists

On Wed, Aug 15, 2018 at 1:06 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Thank you for reporting this bug to Ubuntu.
> Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
>
> See this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> We appreciate that this bug may be old and you might not be interested
> in discussing it any more. But if you are then please upgrade to the
> latest Ubuntu version and re-test. If you then find the bug is still
> present in the newer Ubuntu version, please add a comment here telling
> us which new version it is in and change the bug status to Confirmed.
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Incomplete
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:
> core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2017-10-27 Thread Peter Wallbridge 
Thanks for the info. The answer is yes


On Fri, Oct 27, 2017 at 3:04 AM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> This could be related to OpenGL texture sizes or something similar.
> Unity7 (Compiz) has workarounds to avoid that limitation. And Xfce
> avoids it by not using hardware accelerated compositing at all (last I
> checked). It's not surprising if only Gnome Shell hits a problem like
> this...
>
> Do you get the same bug logging in to "Ubuntu" vs "Ubuntu on Xorg"?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Confirmed
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2017-10-27 Thread Peter Wallbridge 
I see both.

During power up, the messages appear on displays 1 and 3.
The sign in is on screen 2 (primary display).

The display manager shows 3 displays, but after the apply is selected, only
two work.

Why do they work with Xfce and not with gnome?

Thanks

Peter



On Fri, Oct 27, 2017 at 2:20 AM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Thanks. Perhaps we jumped the gun though...
>
> On your login screen do you see two options "Ubuntu" and "Ubuntu on
> Xorg", or only one?
>
> It looks like you might be experiencing a problem with Xorg judging by
> comment #4:
>
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): flip queue failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): Page flip failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
> RADEON(0): present flip failed
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): flip queue failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): Page flip failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
> RADEON(0): present flip failed
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): flip queue failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): Page flip failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
> RADEON(0): present flip failed
>
> ** Bug watch added: GNOME Bug Tracker #789540
>https://bugzilla.gnome.org/show_bug.cgi?id=789540
>
> ** Also affects: mutter via
>https://bugzilla.gnome.org/show_bug.cgi?id=789540
>Importance: Unknown
>Status: Unknown
>
> ** Also affects: xorg-server (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: xorg-server (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: mutter (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2017-10-27 Thread Peter Wallbridge 
Did it. I hope I did it correctly.

On Thu, Oct 26, 2017 at 10:14 PM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Peter, we're here to help. And Sebastien is right... The fastest way to
> a fix for you now is for you to report the bug directly on the Gnome bug
> tracker:  https://bugzilla.gnome.org/
>
> We ask you to do this because the conversation that will happen with the
> Gnome guys needs to be with someone who experiences the problem first-
> hand (yourself).
>
> After a fix is available there we will pull it down to here again for
> release in Ubuntu.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in gnome-shell package in Ubuntu:
>   New
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2017-10-26 Thread Peter Wallbridge 
SEBASTIEN

I reported the bug in Launchpad.

Daniel Van Vugt recorded the bug as bug no 1725836

This only appeared in 17.10 not in 17.04.

Ps. something new. It now works OK if I use the xfce manager

Peter

On Thu, Oct 26, 2017 at 10:48 AM, Sebastien Bacher 
wrote:

> The issue you are reporting is an upstream one and it would be nice if
> somebody having it could send the bug to the developers of the software
> by following the instructions at
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
> tell us the number of the upstream bug (or the link), so we can add a
> bugwatch that will inform us about its status. Thanks in advance.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in gnome-shell package in Ubuntu:
>   New
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1725836] Re: No more than 2 displays

2017-10-24 Thread Peter Wallbridge 
Hi Daniel

When powering up, I see the booting messages on screen 1 an 3.

When signing in I can use screen 2.

After signing in I can only see output on screens 1 and 2.

In the monitor display function all three displays are detected. Screen 2
is the primary display.

If I play around with the monitor display function i can get screen 1 and 2
to work or screen 1 and 3 to work or screen 2 and 3 to work, but I cannot
get all three to work at the same time.

The screen that is not working is blank. If this does not help I can take
some photographs of the screens and send them to you if you wish.

Peter


On Tue, Oct 24, 2017 at 1:06 AM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> What exactly do you see on the third display? Is it off/sleeping?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725836/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs