The same observed with NVIDIA 470.86 driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877226
Title:
nvidia - external display unavailable after screen goes to sleep
To manage notifications ab
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877226
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877226
Title:
nvi
Daniel et al,
I wanted to provide an update based on the latest official mutter
release as of today - 25.Mai.
The issue still exists. However, I provide the following in the event
it helps to refine the underlying issue. Please let me know if there
are logs that would be helpful to you or addit
Will do. Thanks Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877226
Title:
nvidia - external display unavailable after screen goes to sleep
To manage notifications about this bug go to:
h
Thanks. Yes that shows the monitor is still connected but some bug in
(gnome-control-center | mutter | nvidia driver) is preventing it from
being configured properly.
As a first step please subscribe to bug 1874207 and wait until that has
been declared "Fix Released" for focal. I expect an update
Daniel:
I have xrandr before and after and the monitor was detected in both cases. I
ran:
xrandr > before.log #before locking the screen
xrandr > after.log #after locking the screen and the external monitor is no
longer in use
diff before.log after.log which results in:
1,2c1,2
< Screen 0: min
I have seen the error in step 10 before. In my case it was caused by bug
1874207 in mutter so maybe wait for that to be fixed...
Also, next time the external display is "unavailable" please open a
Terminal window and run 'xrandr'. Can you still see the external display
there?
** Tags added: nvid
