[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787861
Title:
Displays not detected/positioned correctly when
disconnected/reconnected
Status in linux package in Ubuntu:
Expired
Bug description:
I just upgraded from Ubuntu 16.04 LTS to 18.04 LTS. Previously, this
was all working correctly: I have 3 displays connected to an nVidia
GT 730. VGA-0 (an old 21-inch CRT) is never enabled (just haven't got
around to removing it). DVI-D-0 is the primary display, always
connected and turned on, in 1920x1080 60hz. HDMI-0 is a secondary
display (actually, linked to my AV receiver and then to my 55" HDTV),
and it is turned on when I want the big screen (1920x1080 60hz,
positioned to the left of the primary), turned off the rest of the
time.
Now, whenever I turn off my secondary HDMI display, my third (VGA)
display is automatically enabled. Furthermore, when I then turn the
secondary display back on, it is set to the wrong mode (interlaced at
30 Hz instead of progressive scan at 60 Hz) and in the wrong position
(to the right of the main display, when I want it to the left).
Running the correct 'xrandr' command to reset all three displays to
the correct conditions instead results in random behavior--instead of
a 3840x1080 screen, with the primary display offset to +1920x0, I
usually end up with both displays set to span the entire 3840x1080
area, offset to +0x0 (so they're mirroring each other). Sometimes the
VGA display remains turned on with a random (not actually displayable)
resolution, sometimes it does not. Trying to force the displays into
the correct mode with further 'xrandr' commands does not work; I have
to reboot the machine to get the displays back to where they belong.
This is the 'xrandr' command that SHOULD reset the displays to the
correct modes/positions (the primary DVI display is already in the
correct mode, so I don't specify that): xrandr --output VGA-0 --off
--output DVI-D-0 --primary --output HDMI-0 --size 1920x1080 --rate 60
--left-of DVI-D-0
Occasionally, it does work correctly, but most of the time, it does
not (see above).
Under 16.04 LTS, I did have an issue for a long time where the
secondary HDMI display would be set to an interlaced mode when I
turned it back on (but otherwise, everything was correct--and a simple
'xrandr -output HDMI-0 --auto' fixed it); that problem was corrected
with a kernel upgrade a short time ago (maybe 3 months?--
unfortunately, I never filed a bug and just lived with it, so I'm not
sure exactly when the problem went away, either).
Attached is the output of 'xrandr' with everything set correctly.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: jonathan 2183 F.... pulseaudio
/dev/snd/controlC1: jonathan 2183 F.... pulseaudio
/dev/snd/controlC0: jonathan 2183 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 15:38:09 2018
HibernationDevice: RESUME=UUID=e0d7d646-78bf-474b-916a-ad6f8523c1b5
InstallationDate: Installed on 2015-08-17 (1098 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: System manufacturer System Product Name
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic
root=UUID=2cd20c22-0c69-4ae2-b81c-11fd8501a2ec ro quiet splash
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:
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago)
dmi.bios.date: 06/14/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0307
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88T-M LE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0307:bd06/14/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88T-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787861/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
