<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bug] Weston-DRM unlock button presented only after mousing over magic coordinates" href="https://bugs.freedesktop.org/show_bug.cgi?id=53181#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bug] Weston-DRM unlock button presented only after mousing over magic coordinates" href="https://bugs.freedesktop.org/show_bug.cgi?id=53181">bug 53181</a> from <a class="email" href="mailto:joe.konno@linux.intel.com" title="Joe Konno <joe.konno@linux.intel.com>"> Joe Konno</a> <pre>(In reply to <a href="show_bug.cgi?id=53181#c4">comment #4</a>) > Can you observe, whether weston-screensaver gets executed or not, and does > your installation have an outdated copy of the weston-screensaver binary > somewhere? I typically do not build weston-screensaver. For this case, I did re-build weston with the screensaver and modify weston.ini accordingly. The screensaver does indeed execute and does not crash or report anything strange. Reported issue applies when weston-screensaver is running. In fact, the issue is more pronounced with screensaver: complete rendering hang until the lock button appears. This calls into question my mention of "magic mouse coordinates" for sure. > > There is something going on with the unlock dialog for sure, originally it > used to be movable and resizeable, and I don't think it is anymore. The > delay of 30 sec to 1 min would hint towards the panel clock updating, and if > that indeed is related, there's some serious confusion in the code. Could > you make the panel clock have seconds, so that it will update every second, > and see if that makes any difference? I think there should be a weston.ini > setting for it. Alas, no weston.ini config option that I could identify, so I tested with "stock" weston (updating every minute) and with locally-modified weston that has a panel displaying %H:%M:%S includes and a redraw_handler timer firing every second. Same behavior seen for each weston build.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>