compiz dies during oem-config and steals the focus so that input fields are unusable

Which text box are you experiencing this with? Onboard is mostly working fine for me (most of the onboard glitches that I experience are with libreoffice).

The text boxes in the initial setup wizard. (Computer name, username, password, etc.) Because of that, I haven't gotten to log in into Unity so I'm not sure about the rest of the OS.

I also want to mention it was working fine in build 20121220.

I am also being affected by this bug, I get to the who are you part of the installation and the onscreen keyboard does not function.

Strangely enough, the bug is gone when I flashed the newest build. (20121222) Everything during installation seems to be fine.

I've been experiencing this with the newest build instead. I am currently re-downloading the image and will try flashing again.

I decided to give a shot and rebooted the nexus again, this time the installation worked. Seems that the issue comes and goes.

I tried to built it yesterday and I got same thing..

I got the same bug on my first boot. After rebooting the tablet i was able to write.

Is there a way to boot into the Ubiquity environment on an already installed Nexus 7? This would help us testing Onboard in the installer and perhaps simplified debugging this issue too.

as long as you dont let it finish (and remove itself which happens at the very end of the installer run), you will always land in oem-config again on boot...

the problem here is (as i wrote in another duplicate bug before) that the focus works just fine on second boot of the installer

the issue started showing up when oem-config/ubiquity was switched from using metacity to use compiz as default WM during the install, i would pretty much suspect there is a race condition between compiz and onboard startup or some such.

I found that sometimes the keyboard would appear automatically, sometimes not. Whether it appeared automatically or not, it would sometimes stop sending input and require a reboot. It took me 4 reboots to finish configuring Ubuntu!

I see, it really only happens on the very first boot of the installation then. I've discovered I can run oem-config-prepare to reboot into the installer. Then in 10 restarts typing always worked. I'll try some real installations another time.

Focus issues were the first thing I suspected too. Which WM is running, or even none at all shouldn't really matter for typing, as long as the right target window is focused. To be sure, we could perhaps confirm that key-strokes are actually sent by monitoring the XTest keyboard device. xinput test-xi2 5, probably.

Rocko, how long ago was that? Did the keyboard fail to appear for entering the user name?

@marmuta: I first tried installing it on the 4th of January, and when I saw comments that it would work after reboot I tried again on the 5th.

On at least one attempt after rebooting the keyboard failed to appear automatically for entering the user name, but on other attempts it did appear automatically. It took me several reboots because the keyboard would sometimes send input after rebooting but then it would stop sending input, and rebooting was the only way of getting it to resend input.

@Rocko, yes, I see what you mean, I can actually reproduce it on every reboot into the installer now. The key is to try long enough. Sometimes it happens right away, sometimes it takes a couple of minutes. I haven't found a clear sequence of taps triggering it, but typing a bit in the "Who are you?" page, then tapping in and around the text entries seems to be quite successful.

When it finally happens, the installer window briefly disappears, then reappears without round corners. Onboard in floating mode loses its round corners too. If the keyboard's window decoration was enabled this is gone as well. Typing won't work from this point, focus is probably lost.

To me that looks like compiz just stops running. I'd like to produce some error output/log file, but haven't been able to get to a terminal yet. There don't seem to be other virtual terminals set up during installation.

I was able to reproduce the error. I am using:

$ uname -a
Linux rigved-laptop 3.1.10-8-nexus7 #19-Ubuntu SMP PREEMPT Wed Jan 2 14:12:08 UTC 2013 armv7l armv7l armv7l GNU/Linux

Select "Show Password" in the Wi-fi oem setup. After this step, unable to enter any text using Onscreen.

Referring to message #16: Should compiz not also be added as an affected project by this bug?

I ran into this bug after trying several installations, and can confirm that it happens when compiz crashes during oem-config. As long as compiz is running (which you can tell by the window border and drop shadow), onboard works as expected. If compiz crashes during startup, however (which seems to happen randomly - sometimes it does, and sometimes it doesn't), onboard will only work with new windows that are opened (such as network preferences) when they gain focus. This is almost certainly a compiz issue.

a) compiz should not crash
b) ubiquity-dm should be able to respawn the wm if it dies

updated the bugtasks accordingly

Status changed to 'Confirmed' because the bug affects multiple users.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1093050

This happens to me on a Panda board.

i've had it happen occasionally in Vbox4.2

On Tue, Feb 26, 2013 at 7:37 AM, Carla Sella <email address hidden>wrote:

> This happens to me on a Panda board.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1122162).
> https://bugs.launchpad.net/bugs/1093050
>
> Title:
> compiz dies during oem-config and steals the focus so that input
> fields are unusable
>
> Status in Onboard on-screen keyboard:
> Invalid
> Status in Ubuntu on the Nexus 7:
> Confirmed
> Status in “compiz” package in Ubuntu:
> Confirmed
> Status in “ubiquity” package in Ubuntu:
> Confirmed
>
> Bug description:
> OnBoard does not launch automatically when a text box is selected.
> Manually launching OnBoard and typing has no functionality on the
> selected text boxes. This also creates some visual artifacts. First
> user encounter was during initial setup (Ubiquity) on build 20121221.
> Rebooting or reflashing seems to fix the issue.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/onboard/+bug/1093050/+subscriptions
>

When this happens and you still have internets/tty1 available it would be great to see if there are any files in /var/crash/* , and if there are any upload each and everyone of them with $ ubuntu-bug /var/crash/*.crash

@Dmitrijs
It happend to me again, but there were no files in /var/crash.
As when this happens I have tty1 available, if you need I can let you have other log files that can help you solve this issue.
I could run ubuntu-bug compiz, but as this bug has not been reported by me I cannot attach any info with apport or ubuntu-bug.
Let me know what log files would be of any help.

Please don't mark bugs as incomplete for no reason.

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.