I got it to work by setting EGL_PLATFORM=x11 when running the compositor.
Not sure why that's necessary, though.
On Sun, Mar 27, 2011 at 12:13 PM, Daniel wrote:
> I have had the same problems. My embedded chip is suposed to work with
> the i915 driver (X.org uses it), but Wayland fails to start.
2011/4/5 Friar
> 2011/4/5 Kristian Høgsberg
>
>> On Tue, Apr 5, 2011 at 5:59 AM, Michal Suchanek
>> wrote:
>> > Hello,
>> >
>> > what is the plan for screensave/screenlocker support in wayland?
>> >
>> > The support in X is a fail in several ways.
>>
>> It sure is. The plan for Wayland is that
2011/4/5 Kristian Høgsberg
> On Tue, Apr 5, 2011 at 5:59 AM, Michal Suchanek
> wrote:
> > Hello,
> >
> > what is the plan for screensave/screenlocker support in wayland?
> >
> > The support in X is a fail in several ways.
>
> It sure is. The plan for Wayland is that the lock screen is just part
On Tue, Apr 5, 2011 at 5:59 AM, Michal Suchanek wrote:
> Hello,
>
> what is the plan for screensave/screenlocker support in wayland?
>
> The support in X is a fail in several ways.
It sure is. The plan for Wayland is that the lock screen is just part
of the compositor. There are no problems wit
Hello,
what is the plan for screensave/screenlocker support in wayland?
The support in X is a fail in several ways.
First off there is no way to select all events. While you can spy on
mouse position or key events you can't spy on mouse events so the
screensaver activates when only mouse buttons
Some months ago, I have discussed the Wayland Crash Scenario and how windows
should reconnect to a newly started wayland either than being closed and
losing the open work.
I discussed with zhasha and daniels and below there is a resumé of some
points that may be useful:
...
wayland doesn't reall