[radeon] No more than 2 displays work simultaneously

Bug #1725836 reported by Peter Wallbridge
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
xorg-server (Ubuntu)
Invalid
Undecided
Unassigned
xserver-xorg-video-ati (Ubuntu)
Invalid
Undecided
Unassigned

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
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: peterw 2037 F.... pulseaudio
 /dev/snd/controlC2: peterw 2037 F.... pulseaudio
 /dev/snd/controlC0: peterw 2037 F.... pulseaudio
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000]
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
   Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356]
HibernationDevice: RESUME=UUID=342f741e-9371-4d2a-8d0a-e6e1a5303015
InstallationDate: Installed on 2018-05-29 (82 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. G1.Sniper B5
Package: xserver-xorg-video-ati 1:18.0.1-1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic N/A
 linux-firmware 1.173.1
RfKill:

Tags: bionic ubuntu ubuntu
Uname: Linux 4.15.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: G1.Sniper B5-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd09/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperB5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperB5-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: G1.Sniper B5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1725836

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
tags: added: multimonitor regression-release
Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Dependencies.txt

apport information

tags: added: apport-collected artful
description: updated
Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : GsettingsChanges.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : JournalErrors.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : ProcEnviron.txt

apport information

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: No more than 2 displays

What exactly do you see on the third display? Is it off/sleeping?

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Changed in mutter (Ubuntu):
status: Incomplete → New
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays

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 <
<email address hidden>> 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
>

summary: - No more than 2 displays
+ No more than 2 displays work simultaneously
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Changed in mutter (Ubuntu):
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote : Re: No more than 2 displays work simultaneously

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.

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

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 <email address hidden>
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
>

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: No more than 2 displays work simultaneously

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.

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

Did it. I hope I did it correctly.

On Thu, Oct 26, 2017 at 10:14 PM, Daniel van Vugt <
<email address hidden>> 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
>

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: No more than 2 displays work simultaneously

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

Changed in xorg-server (Ubuntu):
status: New → Incomplete
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously
Download full text (3.6 KiB)

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 <
<email address hidden>> 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)
> In...

Read more...

Changed in mutter:
importance: Unknown → High
status: Unknown → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: No more than 2 displays work simultaneously

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"?

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

Thanks for the info. The answer is yes

On Fri, Oct 27, 2017 at 3:04 AM, Daniel van Vugt <
<email address hidden>> 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
>

Changed in gnome-shell (Ubuntu):
status: Incomplete → Triaged
Changed in mutter:
status: Confirmed → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: No more than 2 displays work simultaneously

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
Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

I am using 18.04 and bug still exists

On Wed, Aug 15, 2018 at 1:06 AM Daniel van Vugt <
<email address hidden>> 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
>

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: No more than 2 displays work simultaneously

I am using 18.10 the bug still exists.All three displays can be displayed depending on enabling, but never at once.

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

Great, thanks. Can you please run these two commands on the machine and send us their outputs?

  xrandr

  lspci -k

tags: added: bionic cosmic
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Changed in mutter (Ubuntu):
status: Incomplete → New
Changed in xorg-server (Ubuntu):
status: Incomplete → New
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Changed in mutter (Ubuntu):
status: New → Incomplete
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also run:

  glxinfo

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

It appears you already provided 'xrandr' output on bugzilla. Is this still correct?

  Screen 0: minimum 320 x 200, current 5280 x 1080, maximum 16384 x 16384

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously
  • glxinfo.txt Edit (124.3 KiB, text/plain; charset="US-ASCII"; name="glxinfo.txt")
Download full text (10.9 KiB)

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.00 50.00 59.94
   1920x1080i 60.00 50.00 59.94
   1680x1050 59.88
   1600x900 60.00
   1280x1024 75.02 60.02
   1280x960 60.00
   1280x800 59.91
   1152x864 75.00
   1280x720 60.00 50.00 59.94
   1024x768 75.03 60.00
   1024x576 59.97
   832x624 74.55
   800x600 75.00 60.32
   720x576 50.00
   720x576i 50.00
   720x480 60.00 59.94
   720x480i 60.00 59.94
   640x480 75.00 60.00 59.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.02 60.02
   1152x864 75.00
   1024x768 75.03 60.00
   800x600 75.00 60.32
   640x480 75.00 59.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...

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote :
Download full text (12.7 KiB)

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 <email address hidden>
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 <email address hidden>
> 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.00 50.00 59.94
>> 1920x1080i 60.00 50.00 59.94
>> 1680x1050 59.88
>> 1600x900 60.00
>> 1280x1024 75.02 60.02
>> 1280x960 60.00
>> 1280x800 59.91
>> 1152x864 75.00
>> 1280x720 60.00 50.00 59.94
>> 1024x768 75.03 60.00
>> 1024x576 59.97
>> 832x624 74.55
>> 800x600 75.00 60.32
>> 720x576 50.00
>> 720x576i 50.00
>> 720x480 60.00 59.94
>> 720x480i 60.00 59.94
>> 640x480 75.00 60.00 59.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.02 60.02
>> 1152x864 75.00
>> 1024x768 75.03 60.00
>> 800x600 75.00 60.32
>> 640x480 75.00 59.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 Contr...

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote :
Download full text (13.1 KiB)

On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge <email address hidden>
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 <email address hidden>
> 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 <email address hidden>
>> 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.00 50.00 59.94
>>> 1920x1080i 60.00 50.00 59.94
>>> 1680x1050 59.88
>>> 1600x900 60.00
>>> 1280x1024 75.02 60.02
>>> 1280x960 60.00
>>> 1280x800 59.91
>>> 1152x864 75.00
>>> 1280x720 60.00 50.00 59.94
>>> 1024x768 75.03 60.00
>>> 1024x576 59.97
>>> 832x624 74.55
>>> 800x600 75.00 60.32
>>> 720x576 50.00
>>> 720x576i 50.00
>>> 720x480 60.00 59.94
>>> 720x480i 60.00 59.94
>>> 640x480 75.00 60.00 59.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.02 60.02
>>> 1152x864 75.00
>>> 1024x768 75.03 60.00
>>> 800x600 75.00 60.32
>>> 640x480 75.00 59.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 Cor...

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote :
Download full text (13.1 KiB)

On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge <email address hidden>
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 <email address hidden>
> 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 <email address hidden>
>> 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.00 50.00 59.94
>>> 1920x1080i 60.00 50.00 59.94
>>> 1680x1050 59.88
>>> 1600x900 60.00
>>> 1280x1024 75.02 60.02
>>> 1280x960 60.00
>>> 1280x800 59.91
>>> 1152x864 75.00
>>> 1280x720 60.00 50.00 59.94
>>> 1024x768 75.03 60.00
>>> 1024x576 59.97
>>> 832x624 74.55
>>> 800x600 75.00 60.32
>>> 720x576 50.00
>>> 720x576i 50.00
>>> 720x480 60.00 59.94
>>> 720x480i 60.00 59.94
>>> 640x480 75.00 60.00 59.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.02 60.02
>>> 1152x864 75.00
>>> 1024x768 75.03 60.00
>>> 800x600 75.00 60.32
>>> 640x480 75.00 59.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 Cor...

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: No more than 2 displays work simultaneously

GPUs:

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

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Curacao PRO [Radeon R7 370 / R9 270/370 OEM] (rev 81)
Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9
270/370 OEM]
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

Revision history for this message
Daniel van Vugt (vanvugt) 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?

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

Separately, please also try clicking the cog wheel button on the login screen and selecting:

  Ubuntu on Wayland

Does that fix it?

Changed in xserver-xorg-video-ati (Ubuntu):
status: New → Incomplete
Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously
Download full text (4.1 KiB)

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 <
<email address hidden>> 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 ...

Read more...

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote :
Download full text (4.5 KiB)

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 <email address hidden>
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 <
> <email address hidden>> 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 Ubunt...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: No more than 2 displays work simultaneously

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.

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

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 <
<email address hidden>> 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
>

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote :
Download full text (8.8 KiB)

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 ...

Read more...

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote :
Download full text (9.6 KiB)

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 <email address hidden>
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 afte...

Read more...

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote :
Download full text (9.9 KiB)

On Sat, Aug 18, 2018 at 9:07 AM Peter Wallbridge <email address hidden>
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 <email address hidden>
> 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 fini...

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote :
Download full text (10.2 KiB)

On Sat, Aug 18, 2018 at 9:08 AM Peter Wallbridge <email address hidden>
wrote:

>
>
>
>
> On Sat, Aug 18, 2018 at 9:07 AM Peter Wallbridge <email address hidden>
> 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 <email address hidden>
>> 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_aaebdc...

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: No more than 2 displays work simultaneously

Thanks. Comment #33 seems to be the most important one now. If the bug occurs in XFCE as well then this is not a gnome-shell bug. Instead it should be assigned to xorg-server, or the driver, or the kernel.

no longer affects: mutter
no longer affects: gnome-shell (Ubuntu)
no longer affects: mutter (Ubuntu)
summary: - No more than 2 displays work simultaneously
+ [radeon] No more than 2 displays work simultaneously
tags: added: radeon
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1725836

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

Thanks Daniel. Yes it also shows up on xfce

But why does ubuntu still display on monitor 3, but no mor than two
displays?

Peter

On Sun, Aug 19, 2018 at 10:41 PM Daniel van Vugt <
<email address hidden>> wrote:

> Thanks. Comment #33 seems to be the most important one now. If the bug
> occurs in XFCE as well then this is not a gnome-shell bug. Instead it
> should be assigned to xorg-server, or the driver, or the kernel.
>
> ** No longer affects: mutter
>
> ** No longer affects: gnome-shell (Ubuntu)
>
> ** No longer affects: mutter (Ubuntu)
>
> ** Summary changed:
>
> - No more than 2 displays work simultaneously
> + [radeon] No more than 2 displays work simultaneously
>
> ** Tags added: radeon
>
> ** Also affects: linux (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:
> [radeon] No more than 2 displays work simultaneously
>
> Status in linux package in Ubuntu:
> New
> 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/ubuntu/+source/linux/+bug/1725836/+subscriptions
>

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : AlsaInfo.txt

apport information

tags: added: ubuntu
description: updated
Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : CRDA.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Dependencies.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : DpkgLog.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Lspci.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Lsusb.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : MonitorsUser.xml.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : ProcModules.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : PulseList.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : UdevDb.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : WifiSyslog.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : XorgLog.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : XorgLogOld.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : Xrandr.txt

apport information

Revision history for this message
Peter Wallbridge (pgwallbridge-y) wrote : xdpyinfo.txt

apport information

tags: removed: artful cosmic
Revision history for this message
Paul White (paulw2u) wrote :

This bug report has sat with a status of 'Incomplete' for almost four years without further comment so it is being closed as 'Invalid'.

Please feel free to re-open this bug report if this is still an issue when using a currently supported release of Ubuntu or one of its flavours making sure that you tell us in which release(s) you still experience this issue.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in xorg-server (Ubuntu):
status: Incomplete → Invalid
Changed in xserver-xorg-video-ati (Ubuntu):
status: Incomplete → 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.