<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Thanks for the feedback. I'll watch the project for future progress in saving Xapp states but I'm sure it's not much of a priority.<br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div><br></div>--<br>Justin Garrison<br><a href="http://1n73r.net/" target="_blank">1n73r.net</a></div></div>
<br><div class="gmail_quote">On Thu, Feb 26, 2015 at 3:38 AM, Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 02/26/2015 12:42 PM, Ruslan Kuprieiev wrote:<br>
> Hi Justin!<br>
><br>
> Dumping the entire Xserver is problematic, as it uses a variety of devices that we don't currently<br>
> support(i.e. gpu).<br>
<br>
</span>Yes, the major issue would be in ties to hardware the X-server will definitely have.<br>
<span class=""><br>
> It actually looks like dumping Xapp is a lot easier then dumping entire X server,<br>
> still, it requires good knowledge of X internals.<br>
<br>
</span>I wouldn't be such optimistic :) Dumping an X-server might be as easy as doing it<br>
for hybernation. Messing with all the wayland mess can be harder. But I'm not sure :)<br>
<br>
Thanks,<br>
Pavel<br>
<br>
<br>
</blockquote></div><br></div>