<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Regression with Dell TB16 dock and Linux kernel 4.16.x" href="https://bugs.freedesktop.org/show_bug.cgi?id=106250#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Regression with Dell TB16 dock and Linux kernel 4.16.x" href="https://bugs.freedesktop.org/show_bug.cgi?id=106250">bug 106250</a> from <a class="email" href="mailto:stanislav.lisovskiy@intel.com" title="Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>"> Stanislav Lisovskiy</a> <pre>It has been confirmed that correspondent uevent is delivered to the userspace by observing correspondent traces in ddx sna_handle_events gets uevent which is then analyzed by sna_mode_discover which in turn sends the randr notification (RRTellChanged, RRCrtcNotify) to xserver clients. In non-buggy case we get a message ProcRRSetScreenConfig from the desktop clients in response, which then triggers modeset(drm_mode_setcrtc). However this doesn't happen for some reason when bug happens, despite that DRM connector state is the same as in non-buggy case. After discussion with Martin, made a decision that this bug can be closed as non-fixable at least from kernel side and correspondent bug filed for gnome-desktop/Ubuntu.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>