<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Xwayland crashes, display_handle_error, authenticate error inside libwayland-client.so, GUI app autostart whilst being switched to TTY" href="https://bugs.freedesktop.org/show_bug.cgi?id=108038#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Xwayland crashes, display_handle_error, authenticate error inside libwayland-client.so, GUI app autostart whilst being switched to TTY" href="https://bugs.freedesktop.org/show_bug.cgi?id=108038">bug 108038</a> from <a class="email" href="mailto:fourdan@xfce.org" title="Olivier Fourdan <fourdan@xfce.org>"> Olivier Fourdan</a> <pre>(In reply to Pekka Paalanen from <a href="show_bug.cgi?id=108038#c11">comment #11</a>) > Ok, so it's actually related to the problem that wl_drm is still be only way > for a client to know which device the compositor is using. > > Why wouldn't Xwayland look at the device and open the corresponding render > node instead if there is one? Maybe the drmDevice API in libdrm would make > that easy and portable nowadays? Yeap, I reckon it should work, I can give that a try. > Do we have an issue filed anywhere for making a companion extension to > zwp_linux_dmabuf so that clients can find out which device their buffers > should at least work on? Not to my recollection, but maybe ask Daniel or Jonas?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>