[Wayland-bugs] [Bug 65739] weston-launch completely freezes Raspbian

[bugzilla-daemon at freedesktop.org]

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

Pekka Paalanen <ppaalanen at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |---
           Severity|major                       |normal
           Assignee|wayland-bugs at lists.freedesk |ppaalanen at gmail.com
                   |top.org                     |

--- Comment #2 from Pekka Paalanen <ppaalanen at gmail.com> ---
Yeah, not getting any input devices leaves one without any local access to the
RPi. However, all that is frozen really should be just input devices and
output, as long as Weston is running. The ssh server should still work,
allowing to log in remotely and kill weston with SIGTERM, after which the
console should work again.

I'm reopening this bug to serve as a reminder, that I really should make sure
Weston on RPi exits immediately, if it cannot open any input devices. And make
that overridable by a config or command line option.

Ah, the other thing: I should also make sure to handle failure to use VCHIQ
properly.

Actually, I think what happened here is not about input devices, but the VCHIQ
connection, which failed unexpectedly due to lack of permissions, and the
console was not restored, leaving it unusable.

So that's two more items in my TODO, but currently no time to fix. If anyone
wants to work on these, let me know. There are actually lots of little loose
ends with the rpi-backend.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20130614/9989e91c/attachment.html>