[Bug 1195917] New: 2nd display gets blanked after suspende/resume in dual USB display configuration
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 Bug ID: 1195917 Summary: 2nd display gets blanked after suspende/resume in dual USB display configuration Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: SLES 15 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs@suse.de Reporter: rubens.furbetta@suse.com QA Contact: gfx-bugs@suse.de Found By: --- Blocker: --- In a dual-display configuration using USB display containing the DisplayLink technology, after a suspend and then resume cycle the 2nd display gets blanked. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 http://bugzilla.opensuse.org/show_bug.cgi?id=1195917#c1 --- Comment #1 from Rubens Furbetta <rubens.furbetta@suse.com> --- Comments imported from Bug#1188970: guek wu neo 2022-02-14 10:46:27 UTC
Hi Guek, did you try Suspend & Resume ?
suspend & resume should be on different topics of reporting.. Anyhow, the connected Displaylink monitor's port number will change to a new port number upon resume back from suspend. That is nothing displayed on monitor but the power is there. I have used 'xrandr' to direct to the new port. --------------------------------------------------------------------------------------------------- Comment 161 Stefan Dirsch 2022-02-14 10:52:07 UTC (In reply to guek wu neo from comment #159)
Hi Guek, did you try Suspend & Resume ?
suspend & resume should be on different topics of reporting..
Anyhow, the connected Displaylink monitor's port number will change to a new port number upon resume back from suspend. That is nothing displayed on monitor but the power is there.
I have used 'xrandr' to direct to the new port.
Wonderful. :-( Can you provide us the xrandr output before suspend and after resume, please? ----------------------------------------------------------------------------------------------------- Comment 162 guek wu neo 2022-02-14 11:18:49 UTC Created attachment 856132 [details] xrandr before, afterresume and afterworkaround (In reply to Stefan Dirsch from comment #161)
(In reply to guek wu neo from comment #159)
Hi Guek, did you try Suspend & Resume ?
suspend & resume should be on different topics of reporting..
Anyhow, the connected Displaylink monitor's port number will change to a new port number upon resume back from suspend. That is nothing displayed on monitor but the power is there.
I have used 'xrandr' to direct to the new port.
Wonderful. :-( Can you provide us the xrandr output before suspend and after resume, please?
see attached for xrandr, is the direction change. I redirected displaylink monitor to left with reference to primary display(eDP-1). localhost:~ # xrandr --output DVI-I-1-1 --left-of eDP-1 [reply] [���] Private Comment 163 Stefan Dirsch 2022-02-14 11:42:51 UTC xrandr_b4.txt and xrandr_after.txt are identical. In xrandr_after_outputleft.txt the position of eDP-1 and DVI-I-1-1 has been swapped compared to xrandr_after.txt . I don't get exactly what you did and what happened. ----------------------------------------------------------------------------------------------------- Comment 164 Ricardo Lopez Caballero 2022-02-14 11:54:50 UTC (In reply to guek wu neo from comment #159)
(In reply to Ricardo Lopez Caballero from comment #150)
(In reply to guek wu neo from comment #148)
rpm --changeloq -q xorg-x11-server | head -n 5
fyi, also Verified the change log to see Thomas 07Feb change notes that states the fixes.
i didnot paste it here since i have problem to write to the attached usb-stick.
Thank you everyone for the support!
Hi Guek, did you try Suspend & Resume ?
suspend & resume should be on different topics of reporting..
Anyhow, the connected Displaylink monitor's port number will change to a new port number upon resume back from suspend. That is nothing displayed on monitor but the power is there.
I have used 'xrandr' to direct to the new port.
Hi Guek, i'm using SLES15 with GNOME Desktop, the 2nd usb display is detected and working in extended desktop mode, you see the background. In power settings defined that pressing power button it should suspend. After pressing power button and in suspend state, later pressing again power button and if required after logon again, the extended desktop using the 2nd usb display should be visible. Sometimes after resume the 2nd usb display is black showing nothing. I have compared this with SLES12 SP5 but here resume was fine. ----------------------------------------------------------------------------------------------------- Comment 165 guek wu neo 2022-02-14 13:14:54 UTC (In reply to Stefan Dirsch from comment #163)
xrandr_b4.txt and xrandr_after.txt are identical. In xrandr_after_outputleft.txt the position of eDP-1 and DVI-I-1-1 has been swapped compared to xrandr_after.txt . I don't get exactly what you did and what happened.
Upon resume back from Suspend, the connected displaylink monitor(Secondary monitor remains blank black but the primary monitor is normal. To recover blank black displaylink monitor , i would have to execute the xrandr to put the display back. Previously i have noticed the display port of which the displaylink monitor is connected would changed upon resume back from S3.. However from this latest xrandr that i collected using the latest test iso, it seems the display port remain the same yet it appear blank black on the displaylink monitor(Seondary monitor) until i execute the following: 'xrandr --output DVI-I-1-1 --left-of eDP-1' This is the sequence of event to duplicate it: 1. on Desktop -both Primary monitor(built-in) and Secondary monitor(displaylink monitor) is turn on, displaying normally ==> collect 'xrandr_before.txt' 2. put host System to suspend ==> systemctl suspend 3. wake the System from suspend by pressing power button ==>system wake up, see display on Primary monitor but displaylink monitor(Secondary monitor) is blank black. ==> collected - xrandr_after.txt 4. execute 'xrandr --output DVI-I-1-1 --left-of eDP-1' ==> now see display on displaylink monitor(Secondary monitor) - not blank blank. ----------------------------------------------------------------------------------------------------- Comment 166 Stefan Dirsch 2022-02-14 14:05:13 UTC Ah. Ok. For waking up the monitor you changed the monitor layout. Now I understand. 'xrandr --auto' may have the same effect though without changing the layout. Anyway, both can only be called a workaround. And this will be an issue hard to fix. Not sure if Thomas can reproduce it. Probably he won't. Could be that the used desktop can easily workaround this issue by running such an xrandr command after a resume automatically, but I don't know which desktop is being used here ... ----------------------------------------------------------------------------------------------------- Comment 167 guek wu neo 2022-02-14 14:21:38 UTC (In reply to Stefan Dirsch from comment #166)
Ah. Ok. For waking up the monitor you changed the monitor layout. Now I understand. 'xrandr --auto' may have the same effect though without changing the layout. Anyway, both can only be called a workaround. And this will be an issue hard to fix. Not sure if Thomas can reproduce it. Probably he won't. Could be that the used desktop can easily workaround this issue by running such an xrandr command after a resume automatically, but I don't know which desktop is being used here ...
i tried 'xrandr --auto' it does not work this time with this new iso.. but only the '--left-of' or '--right-of' would. GnomeDesktop is used here ----------------------------------------------------------------------------------------------------- Comment 168 Stefan Dirsch 2022-02-14 14:47:17 UTC Oh well. So you need run two commands to have the original layout back. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 Rubens Furbetta <rubens.furbetta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rubens.furbetta@suse.com, | |tzimmermann@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 Rubens Furbetta <rubens.furbetta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ricardo-lopez-caballero@tos | |hibagcs.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 Rubens Furbetta <rubens.furbetta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 Rubens Furbetta <rubens.furbetta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guek.neo@toshibagcs.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 Rubens Furbetta <rubens.furbetta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 Rubens Furbetta <rubens.furbetta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 Rubens Furbetta <rubens.furbetta@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195917 http://bugzilla.opensuse.org/show_bug.cgi?id=1195917#c2 --- Comment #2 from guek wu neo <guek.neo@toshibagcs.com> --- Previously i was needing the --auto and also noticed the port # change(the connected displaylink monitor's) upon recovery from supspend. But for this most recent on, only 1 command if you know what is the display ports of the connected monitor. such as, I redirected displaylink monitor to left with reference to primary display(eDP-1) with: localhost:~ # xrandr --output DVI-I-1-1 --left-of eDP-1 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com