Thanks, Brian. That solved the problem for me as well. So I guess the
bug is that it has to be set in two different places, in unity-tweak-
tool and in ccsm. At least there's an easy workaround so I don't have
to keep killing nautilus.
--
You received this bug notification because you are a me
Another piece of info: the X client that prevents sloppy mode from
working is "nautilus". Killing nautilus makes the root window behave
normally and not grab the focus.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Adding more info:
The problem is that what's visible as the root window isn't really the
root window. It has some X client running on top of it, so it gets the
focus as the mouse enters it. I verified this by running xkill and
clicking the root window. It actually killed something, which wouldn
I'm testing it with the latest 16.04 update, running Unity.
I open a terminal, move the mouse into it, so it focuses and I can type
into the terminal. Then I move the mouse out of the window, to the root
window (no other window exists). I see the terminal lose focus, and if
I type anything, the
Public bug reported:
Switching to "sloppy" focus mode doesn't work and behaves like "mouse
mode".
I switched using unity-tweak-tool by going to Workspace Settings ->
Additional -> Focus mode. Both "mouse" and "sloppy" result in the same
behavior, with focus following mouse and not focusing on an
I'm aware of the third party PPA workaround, but:
a) I'm not really sure it can be trusted (I don't know Alex Shkop, sorry)
b) I'm certain most people install Chromium from Canonical's repositories
rather than PPA (Official or non-official). These people browse the Web with
browsers that have kno
*** This bug is a security vulnerability ***
Public security bug reported:
The current chromium-browser version in 12.04 is outdated
(http://packages.ubuntu.com/precise/chromium-browser is at version 18 when
current version is 23).
That were most probably security vulnerabilities that where fix
Running W520 - Nvidia quadro 2000M, 16GB, 11.10 x64
Turning on VT-d option in the BIOS cause the system to fail to boot at all.
Turned off VT-d, and everything works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
In your kernel tree, run "patch -p1 < patch.file" and rebuild your
kernel as you would without the patch. In fact, you only have to
rebuild the usbhid.ko module after applying the patch.
--
Remote Control not working (Aureal / Cy se W-01RN)
https://bugs.launchpad.net/bugs/607062
You received thi
To help people searching for a solution for this remote, let's mention
the model here: PHX01RN
--
Remote Control not working (Aureal / Cy se W-01RN)
https://bugs.launchpad.net/bugs/607062
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Franco Catrin's patch solves the problem for new kernels. The attached
patch does the same for 2.6.24, used on 8.04 (Hardy). Thanks Franco!
** Patch added: "Backport of Franco Catrin's patch for older kernels"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607062/+attachment/1718920/+
11 matches
Mail list logo
