Bug 80019 - intel-virtual-output not proxying xrandr/(un)plug events correctly
Summary: intel-virtual-output not proxying xrandr/(un)plug events correctly
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium enhancement
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
Depends on:
Reported: 2014-06-14 09:21 UTC by main.haarp
Modified: 2019-11-27 13:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

i-v-o debug log (1.18 KB, text/plain)
2014-06-14 09:21 UTC, main.haarp
no flags Details

Description main.haarp 2014-06-14 09:21:33 UTC
Created attachment 101037 [details]
i-v-o debug log


I'm noticing some more bugs in intel-virtual-output. The setup is the same as in bug 79994.

When I first start the discrete GPU and i-v-o with no outputs connected, then plug in a display, this display will still show as disconnected in
$ xrandr
however, when I run
$ xrandr -d :8
i-v-o then correctly declares it as connected on :0. Shouldn't running xrandr on :0 suffice for i-v-o to proxy that query to :8?

Additionally, when I disconnect the display, :0 is also not notified until I run
$ xrandr -d :8
at which point i-v-o runs into a bug and stops functioning properly (see the attached log)
Comment 1 Chris Wilson 2014-06-14 12:45:39 UTC
Ah, if it is not happening until you run xrandr -d :8, it is the nvidia GPU not performing hotplug detection and sending that event onwards.

Unfortunately, I haven't thought of a way to detect when crandr is run on :0 to then query :8 instead.
Comment 2 Martin Peres 2019-11-27 13:33:52 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/31.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.