[Bug 91929] Missing RandR events on hotplug

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Sep 10 01:52:04 PDT 2015


https://bugs.freedesktop.org/show_bug.cgi?id=91929

--- Comment #7 from Loïc Yhuel <loic.yhuel at gmail.com> ---
Kscreen doesn't run in kwin, but in kded5 (decides which config to apply), and
kscreen_backend_launcher (XRandR calls). These two parts communicate over DBus.

So you have XRandR events from hotplug, which generate DBus signals from the
backend to the daemon, which calls the backend, which generates other events...


It doesn't use xcb_randr_get_screen_info (only for XRandR 1.1 backend).

It uses xcb_randr_get_screen_resources, but only once. After it uses
xcb_randr_get_screen_resources_current (see
https://quickgit.kde.org/?p=libkscreen.git&a=blob&h=fae1dcc971d5d3a16e95bfa745d6822c69fa2a55&hb=effd39e2ebe767868660b52a8758873e45e4c656&f=backends%2Fxrandr%2Fxrandr.cpp).
So it doesn't do a full reprobe (RRGetInfo).


On XRROutputChangeNotifyEvent with RR_Connected, it will call
XRandROutput::update -> XRandROutput::init -> XRandROutput::updateModes, which
uses xcb_randr_get_screen_resources_current.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150910/f65ed675/attachment.html>


More information about the intel-gfx-bugs mailing list