I would say don't change anything right now. 10 seconds is better, and feels less like a system-wide freeze than 30 seconds does. However if we reduce the Mir timeout to 10 seconds right now we'll just get an increased volume of crash reports.
So... don't change anything. Wait until we fix this without needing such delays. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1536662 Title: [regression] Mir hangs and then crashes due to reading from /dev/random Status in Mir: In Progress Status in Unity System Compositor: In Progress Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: New Bug description: cookie_factory attempts to read data from /dev/random at boot, and blocks until it has enough random data or timesout after 30 seconds. How I can reproduce 1. Run the Unity8 greeter as a mir server 2. Reboot Expected behavior: Greeter is displayed as mir && USC run happily Actual behavior: Mir throws an exception after 30 seconds Work-around: Before logging in, move the mouse around lots, for at least 20 seconds. And after logging in, while you're looking at a black screen, move the mouse around furiously. This will populate the kernel entropy pool sufficiently to avoid the hang and crash. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1536662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
