Super + p does not work as expected, it's defective

[Jeremy]

I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens.

When using super+p there are 4 options:

- Mirror
- Join
- External
- Built-in

The first two options work correctly, but the 3rd and 4th options do not.

External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case.

I am using:
- Ubuntu 4.15.0-47.50-generic 4.15.18
- GeForce GTX 1080/PCIe/SSE2
- I have attached: lspci-vnvn.log

Description: Ubuntu 18.04.2 LTS
Release: 18.04

With nvidia-driver-418 from: ppa:graphics-drivers/ppa

$ apt-cache policy nvidia-driver-418
nvidia-driver-418:
  Installed: 418.56-0ubuntu0~gpu18.04.1
  Candidate: 418.56-0ubuntu0~gpu18.04.1
  Version table:
 *** 418.56-0ubuntu0~gpu18.04.1 500
        500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

I am not sure if this is actually necessary because I don't think this has to do with the graphics card.

I am not sure what other information you will need for this report. I can provide more data upon request.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: jpsimkins 3108 F.... pulseaudio
 /dev/snd/controlC1: jpsimkins 3108 F.... pulseaudio
 /dev/snd/controlC0: jpsimkins 3108 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-06-22 (298 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-47-generic N/A
 linux-backports-modules-4.15.0-47-generic N/A
 linux-firmware 1.173.3
Tags: bionic
Uname: Linux 4.15.0-47-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/03/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97X-UD5H
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.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z97X-UD5H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1825071

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.

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Jeremy (son9ne-junk)]

apport information

[Kai-Heng Feng (kaihengfeng)]

I don't think it's a kernel issue, have you tried Disco?

[Sebastien Bacher (seb128)]

Could you add your journalctl log to the bug after trying the configuration that does work? Does it work if you change the config from gnome-control-center?

[Jeremy (son9ne-junk)]

It seems that the only option that works as expected is the Mirror option. If I use Join as I am already on Join, then I lose my settings.

I have to use gnome-control-center to reconfigure my settings. So this system works but this does not allow me to alter projector mode (super + p), I just have to disable a monitor (this is what I am currently doing).

If I disable a monitor then re-enable it later, I also have to redo my settings (this one may be expected though).

My journalctl when using Mirror (which "works"):

-- Logs begin at Fri 2018-06-22 14:57:18 EDT, end at Wed 2019-04-17 23:34:23 EDT. --
Jun 22 14:57:18 Zeus kernel: microcode: microcode updated early to revision 0x24, date = 2018-01-21
Jun 22 14:57:18 Zeus kernel: Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18)
Jun 22 14:57:18 Zeus kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
Jun 22 14:57:18 Zeus kernel: KERNEL supported cpus:
Jun 22 14:57:18 Zeus kernel: Intel GenuineIntel
Jun 22 14:57:18 Zeus kernel: AMD AuthenticAMD
Jun 22 14:57:18 Zeus kernel: Centaur CentaurHauls
Jun 22 14:57:18 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 22 14:57:18 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 22 14:57:18 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 22 14:57:18 Zeus kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jun 22 14:57:18 Zeus kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Jun 22 14:57:18 Zeus kernel: e820: BIOS-provided physical RAM map:
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000b172dfff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000b172e000-0x00000000b1734fff] ACPI NVS
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000b1735000-0x00000000b2664fff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000b2665000-0x00000000b2f1afff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000b2f1b000-0x00000000da094fff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000da095000-0x00000000da126fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000da127000-0x00000000da18cfff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000da18d000-0x00000000da2d1fff] ACPI NVS
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000da2d2000-0x00000000def39fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000def3a000-0x00000000deffefff] type 20
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 0x00000000defff000-0x00000000defff...

[Jeremy (son9ne-junk)]

Further tinkering, shows that External and Built-in do nothing but make my monitors go blank (refresh).

If I select any of those while on Mirror, I remain on mirror. The same goes for Join.

This is very strange behavior

[Jeremy (son9ne-junk)]

I will test with Disco but as this is a work environment for me I need something a bit more stable than a Beta. I will test with a Live USB and see if this behaves the same.

[Jeremy (son9ne-junk)]

Wow.. just realized I forget to use -r... Sorry about that.

Attached is the output when I Select Mirror which "works"

[Jeremy (son9ne-junk)]

So now that I have been playing a bit more, I found this out.

If I do not reconfigure my monitors after this resets it all. Built-in and External do nothing at all. The screen does not go black or anything. There is no output in journalctl.

If I do configure my system, then switch to built-in, it does nothing. If I switch to External, then it clears out my settings and outputs:

-- Logs begin at Fri 2018-06-22 14:57:18 EDT, end at Thu 2019-04-18 00:00:47 EDT. --
Apr 18 00:00:47 Zeus sudo[21299]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 18 00:00:47 Zeus sudo[21299]: jpsimkins : TTY=pts/1 ; PWD=/home/jpsimkins ; USER=root ; COMMAND=/bin/journalctl -r
Apr 18 00:00:46 Zeus sudo[21182]: pam_unix(sudo:session): session closed for user root
Apr 18 00:00:40 Zeus rtkit-daemon[2437]: Supervising 5 threads of 1 processes of 1 users.
Apr 18 00:00:40 Zeus rtkit-daemon[2437]: Successfully made thread 21254 of process 3108 (n/a) owned by '1000' RT at priority 5.
Apr 18 00:00:40 Zeus rtkit-daemon[2437]: Supervising 4 threads of 1 processes of 1 users.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ffef19050), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff58ad310), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff49b2850), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff2c05090), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff5459040), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ffebbd220), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff815f030), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff62cf560), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff793dde0), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff9e48fb0), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff22e38e0), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff7d62290), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff4abb450), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff4d368b0), has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ffeb90560), has been already finalized. Impossible to set any property ...

[Jeremy (son9ne-junk)]

I just tested with Disco, the exact same thing on there too.

[Jeremy (son9ne-junk)]

Not sure if this is anything but the monitors are numbered 1,2,3 respectively. On Disco, these are reverse of what I have now. Meaning, 3 is now 1 and 1 is now 3. I also noticed this is true for Windows 10 also. Just wanted to make note on this as I am unsure why. Windows 10 projector works but due to the monitor numbers being reverse, the monitors are off too (but it does work on Win10)

[Jeremy (son9ne-junk)]

I also checked this on my office workstation which has a similar setup but different GFX card. The exact issue happens there. I think this is how this works in general in Ubuntu.

[Jeremy (son9ne-junk)]

To clarify, I am running Ubuntu 4.15.0-47.50-generic 4.15.18 at my office

[Kai-Heng Feng (kaihengfeng)]

Does it work if you use `xrandr` command manually?

[Jeremy (son9ne-junk)]

I am not aware of `xrandr` used for projector mode. I have no issues with setting my monitors positions and screen resolution. The issue is when I use Super + p (projector mode) to switch between the 4 mode types:

- Mirror
- Join
- External
- Built-in

If `xrandr` can toggle projector mode, I am not aware of how and I could not find anything in the man. Any assistance is appreciated.

Super + p does not work as intended for 18+ currently (worked for me on 14 and 16) This may be an issue with Gnome, I will try another Gnome desktop flavor to see if this is the case. May take me a day or 2 to respond as I have a heavy workload the next few weeks

[Kai-Heng Feng (kaihengfeng)]

https://wiki.gentoo.org/wiki/Xrandr#Screen_manipulation

[Jeremy (son9ne-junk)]

To answer your question, yes I can setup my monitors with `xrandr` but I can also setup my monitors just fine the default way. The issue has nothing to do with configuring my monitors. When using Super + p after I used `xrandr` to configure my monitors, all configurations were lost just as they were with the normal way of configuring the monitors (`gnome-control-center`)

`xrandr` is not used for projector mode as that documentation is only used to configure the monitors, not control projector mode.

Configuring my monitors is not what my issue is about. My monitors are setup properly. The only issue with setup is that since the migration from 16 to 18, my monitor IDs are in reverse order. Meaning, what was originally ID 0 is now ID 4.

e.g. DP-0, DP-2, DP-4 are what I am currently using. In Ubuntu 16, my monitors were in this order of setup:
- DP-2, DP-0, DP-4

Since the update to Ubuntu 18 this is the new IDs for monitors in the exact same setup
- DP-2, DP-4, DP-0

You can see that DP-4 and DP-0 are switched due to the IDs being in reverse order for some reason.
But I digress as this is important to make note but this is not the issue I am reporting.

The issue I am reporting has to do with Super + p (projector mode) not working as expected. I think this ID order being reversed is part of the problem but this issue seems to be bigger. Super + p which controls the output for Projector mode simply does not work. The only part that works is the Mirror option.

- Join
- External
- Built-in

Do the exact same thing. They wipe out my monitor config and do nothing else. They do not disable any monitors (built-in and external should do this) and when I select Join, I expect to go back to my config as this is what the monitors were configured in but since my configs are reset, nothing happens.

[Sebastien Bacher (seb128)]

How do you use the keybinding? It starts sounding a bit like https://gitlab.gnome.org/GNOME/gnome-shell/commit/fcdac69e ... do you hold the modifier and press several time p while holding it?

[Jeremy (son9ne-junk)]

The kebinding is used by holding down Super then you press p. You see a menu that you again press p while holding down the super key to select your option.

While the issue does sound similar, this is specifying an incompatibility issue which is not the case here. I am using a Gigabyte board and there are no keybindings for Super + p other than the projector mode (which he is calling presentation mode, I like that better).

Seeing the reference to the mutter ticket (https://gitlab.gnome.org/GNOME/mutter/issues/281), this seems to be the issue for me. I see that it has been merged in 6 months ago but I still have the issue. I guess it may not be upstream yet?

[E-Korn (emiliopedrollo)]

It is 2021, I'm using 20.04 and still have the very same behavior described by Jeremy almost 2 years ago.

[Daniel van Vugt (vanvugt)]

This bug is closed as a duplicate of another bug, which is also closed.

If you have any trouble then please open a new bug.