Interacting with window requires moving it to get focus

[Lennart Weller]

Any window in unity needs to be moved before you can see changes.
e.g. You type something in the chat client but you won't actually see the text being typed until you moved the window once. After the first time it behaves as it should. If the window looses focus you have to redo the procedure. Switching between ttys also helps.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity 4.12.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,move,grid,vpswitch,snap,copytex,mousepoll,place,shift,regex,resize,gnomecompat,unitymtgrabhandles,session,animation,wall,expo,workarounds,ezoom,fade,switcher,scale,unityshell]
Date: Sun Sep 4 20:17:40 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
ProcEnviron:
 SHELL=/usr/bin/zsh
 PATH=(custom, user)
 LC_MESSAGES=de_DE.UTF-8
 LANG=de_DE.UTF-8
 LANGUAGE=de:en
SourcePackage: unity
UpgradeStatus: Upgraded to oneiric on 2011-07-14 (52 days ago)

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Moreover it will be really useful if you attach a video of the problem, try to login to a guest session just to confirm if the issue happens there as well. I have not seen this issue.

[Lennart Weller (lhw)]

I tried recording it now. Interestingly enough I can't.
The recordmydesktop program is actually able to capture the text being
written: http://lhw.ring0.de/movs/ubuntu-841247.ogv
In the video I start frantically moving the cursor as soon as the
symbols stop appearing on the screen and I can't see them till the
moment I moved the window. Which means I could see the first to f's
appearing but then none till the end.

P.S. The bug report window is related to #807950 and was not related to
this bug report. It just can't be submitted.

Am 05.09.2011 13:33, schrieb Omer Akram:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
>
> * Is this reproducible?
> * If so, what specific steps should we take to recreate this bug?
>
> This will help us to find and resolve the problem.
>
> Moreover it will be really useful if you attach a video of the problem,
> try to login to a guest session just to confirm if the issue happens
> there as well. I have not seen this issue.
>
> ** Also affects: unity
> Importance: Undecided
> Status: New
>
> ** Changed in: unity
> Status: New => Incomplete
>
> ** Changed in: unity (Ubuntu)
> Status: New => Incomplete
>

[Lennart Weller (lhw)]

I tested the guest session the bug does not appear. So it's related to old settings or applications.

[Omer Akram (om26er)]

I am not sure how to proceed with this bug so I'll be setting it back to NEW and leave for others to have a say or we could close it as invalid ;-)

[Lennart Weller (lhw)]

This is a really awkward bug. It still happens after I completely reset
my homedir (rm -rf). So its definitly not settings related. I now also
tested unity2D and the normal unity is the only window manager which has
this problem.
On 06.09.2011 02:12, Omer Akram wrote:

[Doug McMahon (mc3man)]

It's quite understandable if you consider this comment irrelevant but -
On a very similar install to yours, 11.04 upgraded to 11.10 during A1, over time there were many instances of behavior not consistent with fresh, current installs. So much so that eventually I did dump that install & do over fresh

[Launchpad Janitor (janitor)]

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

[Lennart Weller (lhw)]

I was also able to confirm this bug with gnome-shell on Intel Integrated Graphics. So maybe its related to compiz.

[Omer Akram (om26er)]

gnome-shell does not use compiz, it uses mutter so that makes this bug specific to your hardware of in a deeper component of Ubuntu desktop other than window manager.