I originally encountered this with yesterdays iso-testing build, but I performed at least 2 more tests and it didn't happen again. So that was a total of 3 installation tests with the same disc, all 3 starting from the live desktop and only one resulted in this bug.
I ran 4 more tests with the first of todays iso-testing builds, one of which I aborted, and this bug never appeared.
Then when the second iso-test build was released I ran two more successful installs and only one resulted in this bug. Both of those tests were "side-by-side" installs.
So two out of nine installs result in this bug using three different isos and ATM I can't come up with a method to continuously reproduce the bug.
I should however point out that Alt>SysReq>B does not reboot, but rather brings up the screenshot tool. Alt>SysReq>K does take you back to gdm so you can then reboot from there. Since it's only happened twice I can't be sure, but I'd think sudo reboot should also work.
I'm not sure if this is worth a mention in the Beta1 release notes or not but I'm subscribing the Release Team so they can decide.
This is gonna be a tough one!
I originally encountered this with yesterdays iso-testing build, but I performed at least 2 more tests and it didn't happen again. So that was a total of 3 installation tests with the same disc, all 3 starting from the live desktop and only one resulted in this bug.
I ran 4 more tests with the first of todays iso-testing builds, one of which I aborted, and this bug never appeared.
Then when the second iso-test build was released I ran two more successful installs and only one resulted in this bug. Both of those tests were "side-by-side" installs.
So two out of nine installs result in this bug using three different isos and ATM I can't come up with a method to continuously reproduce the bug.
I should however point out that Alt>SysReq>B does not reboot, but rather brings up the screenshot tool. Alt>SysReq>K does take you back to gdm so you can then reboot from there. Since it's only happened twice I can't be sure, but I'd think sudo reboot should also work.
I'm not sure if this is worth a mention in the Beta1 release notes or not but I'm subscribing the Release Team so they can decide.
Sorry to be a pain and thanks in advance.