The attached screenshots show 2 things I’ve noticed in the latest update:

The attached screenshots show 2 things I’ve noticed in the latest update:

1. Some things aren’t getting imported from ll home on a new LLX install. The colored screenshot is the way ll home was set up. I got the message from LlX that the LL home installation has been detected and would be imported, but 2nd screenshot shows what actually happened.

manually restored the desktop from backup, and it was fine.

2. After screen timeout, the third screenshot is what I got..(totally black nothing, no response to menu key etc.)

It was only one desktop, no lock screen, but it looks like llx was locked up anyway.

The archive’s at this link if you want to download it and take a look …

http://ubuntuone.com/5i9zPTWthTFqFrF7OyW8pY

EDIT: The problem went away when I added a desktop with an unlock shortcut on it.

Pierre Hébert is there any other information you need to fix this one?

http://ubuntuone.com/7SksEKuQugIz2GdgssBp3r

]]>
« (Previous Post)

3 Commentsto The attached screenshots show 2 things I’ve noticed in the latest update:

  1. Anonymous says:

    < ![CDATA[

    +Gábor Barta had the same problem recently regarding the importation. After investigation it appeared the LL setup contained LLX data, and upon importation into LLX, as it doesn’t looks like a LL setup, the migration failed. Could it be that you reloaded into LL a LLX backup ? Anyway I think I will have to handle the LLX to LLX import !


    Regarding the black screen issue, is it a reproducible problem using your archives ?

    ]]>

  2. Anonymous says:

    < ![CDATA[

    Pierre Hébert re LL vs llx backups yes, they were mixed, deliberately. I figured if it were to cause a problem, one would prefer to see in the beta than in a production version. Sorry I left out that bit of info.



    Re the black screen that was reproducible across two devices. It happened every time the screen was turned off. As if LL wasnlooking for a lockscreen that wasn’t there. Solved by adding a second desktop and setting it to lockscreen.


    ]]>

  3. Anonymous says:

    < ![CDATA[

    Many thanks! I understand what is wrong, and that’s easy to understand after all: the template is exported without the lockscreen desktop, but LL keeps in its app configuration the lockscreen id. When locking the screen, a new desktop is created on the fly in place of the previous lockscreen, and of course this new empty desktop is non responsive and useless !


    I need to make sure that the lockscreen id is reset if the lockscreen is not exported

    ]]>

Leave a Reply

Your email address will not be published. Required fields are marked *